Michael Wu wrote:
On Monday 23 April 2007 16:58, Andy Green wrote:
Couldn't get this to apply on current wireless-dev, and there is a
trailing whitespace. Maybe it's a problem with a script I concocted to
extract the patch from saved Thunderbird 2.0 mails... ? Is it just that
wireless-dev changed inbetweentimes?
This patch series depends on the recent cfg80211/mac80211 rtnl locking
patches.
Thanks for that. I added
cfg80211_nl80211-use-rtnl.patch
mac80211-update-for-cfg80211-rtnl-locking.patch
(these names are made from the originally posted subject line) before
your series and they went in fine. And the injection patches went in
fine on top of that, and continue to work.
However I saw this on reinsertion of zd1211rw-mac80211 module:
=============================================
[ INFO: possible recursive locking detected ]
2.6.21-rc7 #11
---------------------------------------------
ip/2600 is trying to acquire lock:
(&dev->_xmit_lock){-+..}, at: [<e09199c5>]
ieee80211_set_multicast_list+0x46/0x167 [mac80211]
but task is already holding lock:
(&dev->_xmit_lock){-+..}, at: [<c05abc05>] dev_mc_upload+0x14/0x3c
other info that might help us debug this:
2 locks held by ip/2600:
#0: (rtnl_mutex){--..}, at: [<c0609593>] mutex_lock+0x21/0x24
#1: (&dev->_xmit_lock){-+..}, at: [<c05abc05>] dev_mc_upload+0x14/0x3c
stack backtrace:
[<c0405ea6>] show_trace_log_lvl+0x1a/0x2f
[<c0406456>] show_trace+0x12/0x14
[<c04064da>] dump_stack+0x16/0x18
[<c04428c7>] __lock_acquire+0x116/0xb46
[<c04436b8>] lock_acquire+0x56/0x6f
[<c060a7d1>] _spin_lock+0x2b/0x38
[<e09199c5>] ieee80211_set_multicast_list+0x46/0x167 [mac80211]
[<c05abad8>] __dev_mc_upload+0x20/0x22
[<c05abc18>] dev_mc_upload+0x27/0x3c
[<c05a9e79>] dev_open+0x47/0x66
[<c05a87b9>] dev_change_flags+0x51/0xf1
[<c05e60c4>] devinet_ioctl+0x235/0x53b
[<c05e6684>] inet_ioctl+0x73/0x91
[<c059f531>] sock_ioctl+0x1ac/0x1c9
[<c048464a>] do_ioctl+0x22/0x67
[<c04848e1>] vfs_ioctl+0x252/0x265
[<c048493d>] sys_ioctl+0x49/0x64
[<c0404eec>] syscall_call+0x7/0xb
-Andy
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
