lkml.org 
[lkml]   [2005]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Subject[PATCH] fix boot hang on some architectures
    From
    Date
    Well, this is a brown paper bag for someone.  The new protocol
    registration locking uses a rwlock to limit access to the protocol list.
    Unfortunately, the initialisation:

    static rwlock_t proto_list_lock;

    Only works to initialise the lock as unlocked on platforms whose unlock
    signal is all zeros. On other platforms, they think it's already locked
    and hang forever.

    Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>


    ===== net/core/sock.c 1.67 vs edited =====
    --- 1.67/net/core/sock.c 2005-03-26 17:04:35 -06:00
    +++ edited/net/core/sock.c 2005-04-02 13:37:20 -06:00
    @@ -1352,7 +1352,7 @@

    EXPORT_SYMBOL(sk_common_release);

    -static rwlock_t proto_list_lock;
    +static DEFINE_RWLOCK(proto_list_lock);
    static LIST_HEAD(proto_list);

    int proto_register(struct proto *prot, int alloc_slab)

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-04-06 13:31    [W:4.576 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site