Re: Warning triggered by lockdep checks for sock_owned_by_user on linux-next-20160420

2016-04-25 Thread Shi, Yang
On 4/22/2016 9:50 PM, Eric Dumazet wrote: On Fri, 2016-04-22 at 21:02 -0700, Shi, Yang wrote: Hi David, When I ran some test on a nfs mounted rootfs, I got the below warning with LOCKDEP enabled on linux-next-20160420: WARNING: CPU: 9 PID: 0 at include/net/sock.h:1408 udp_queue_rcv_skb+0x3d0/0

Re: Warning triggered by lockdep checks for sock_owned_by_user on linux-next-20160420

2016-04-22 Thread Eric Dumazet
On Fri, 2016-04-22 at 21:02 -0700, Shi, Yang wrote: > Hi David, > > When I ran some test on a nfs mounted rootfs, I got the below warning > with LOCKDEP enabled on linux-next-20160420: > > WARNING: CPU: 9 PID: 0 at include/net/sock.h:1408 > udp_queue_rcv_skb+0x3d0/0x660 > Modules linked in: > C

Warning triggered by lockdep checks for sock_owned_by_user on linux-next-20160420

2016-04-22 Thread Shi, Yang
Hi David, When I ran some test on a nfs mounted rootfs, I got the below warning with LOCKDEP enabled on linux-next-20160420: WARNING: CPU: 9 PID: 0 at include/net/sock.h:1408 udp_queue_rcv_skb+0x3d0/0x660 Modules linked in: CPU: 9 PID: 0 Comm: swapper/9 Tainted: G D 4.6.0-rc4-next-2016