The patch titled
lock validator: netlink.c netlink_table_grab fix
has been added to the -mm tree. Its filename is
lock-validator-netlinkc-netlink_table_grab-fix.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: lock validator: netlink.c netlink_table_grab fix
From: Frederik Deweerdt <deweerdt@xxxxxxx>
akpm: It's not clear that this is the right fix. Was this an ipw2200
problem??
Signed-off-by: Frederik Deweerdt <frederik.deweerdt@xxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Cc: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Cc: "Zhu, Yi" <yi.zhu@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
net/netlink/af_netlink.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff -puN net/netlink/af_netlink.c~lock-validator-netlinkc-netlink_table_grab-fix net/netlink/af_netlink.c
--- 25/net/netlink/af_netlink.c~lock-validator-netlinkc-netlink_table_grab-fix Fri Jun 2 13:58:45 2006
+++ 25-akpm/net/netlink/af_netlink.c Fri Jun 2 13:58:45 2006
@@ -157,7 +157,7 @@ static void netlink_sock_destruct(struct
static void netlink_table_grab(void)
{
- write_lock_bh(&nl_table_lock);
+ write_lock_irq(&nl_table_lock);
if (atomic_read(&nl_table_users)) {
DECLARE_WAITQUEUE(wait, current);
@@ -167,9 +167,9 @@ static void netlink_table_grab(void)
set_current_state(TASK_UNINTERRUPTIBLE);
if (atomic_read(&nl_table_users) == 0)
break;
- write_unlock_bh(&nl_table_lock);
+ write_unlock_irq(&nl_table_lock);
schedule();
- write_lock_bh(&nl_table_lock);
+ write_lock_irq(&nl_table_lock);
}
__set_current_state(TASK_RUNNING);
@@ -179,7 +179,7 @@ static void netlink_table_grab(void)
static __inline__ void netlink_table_ungrab(void)
{
- write_unlock_bh(&nl_table_lock);
+ write_unlock_irq(&nl_table_lock);
wake_up(&nl_table_wait);
}
_
Patches currently in -mm which might be from deweerdt@xxxxxxx are
lock-validator-netlinkc-netlink_table_grab-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
