Search Linux Wireless

Re: [ath5k-devel] ath5k hang up in mesh mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > [  577.639420] Mesh plink with 00:19:e0:86:0f:2f ESTABLISHED
> > [  602.864544] BUG: sleeping function called from invalid context at
> > mm/slab.c:3043
> > [  602.869975] in_atomic():1, irqs_disabled():0
> > [  602.874241] INFO: lockdep is turned off.
> > [  602.878162] Pid: 5160, comm: ath5k_pci Not tainted
> > 2.6.27-rc1-wl-14922-gb73da91 #4
> > [  602.885719]  [<c0172e5f>] kmem_cache_alloc+0xef/0x110
> > [  602.890794]  [<c04e9908>] mesh_path_add+0xb8/0x2f0
> > [  602.895610]  [<c04e9908>] mesh_path_add+0xb8/0x2f0
> > [  602.900468]  [<c04eb8c6>] hwmp_route_info_get+0x406/0x4c0
> > [  602.905886]  [<c04eb4e5>] hwmp_route_info_get+0x25/0x4c0
> > [  602.911927]  [<c04eb9f4>] mesh_rx_path_sel_frame+0x74/0x870
> > [  602.917257]  [<c04d76dd>] ieee80211_rx_bss_info+0x67d/0xe80
> > [  602.922846]  [<c04d70dc>] ieee80211_rx_bss_info+0x7c/0xe80
> > [  602.928353]  [<c04d9d40>] ieee80211_rx_mgmt_action+0x180/0x8a0
> 
> I guess mesh_path_add should be using GFP_ATOMIC instead of GFP_KERNEL, since
> it's called under rcu_read_lock?  CCed Johannes.

Looks like it, but I don't really know. OTOH, we really could make all
that RX business non-atomic. Oh well, not now.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux