[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51f7ccd1-6c80-d902-1a19-b885b5f88c24@gmail.com>
Date: Tue, 7 Nov 2017 09:29:25 +0900
From: David Ahern <dsahern@...il.com>
To: valdis.kletnieks@...edu, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: IPv6 issue in next-20171102 - lockdep and BUG handling RA packet.
On 11/7/17 5:56 AM, valdis.kletnieks@...edu wrote:
> I've hit this 6 times now, across 3 boots:
>
> Nov 3 11:04:54 turing-police kernel: [ 547.814748] BUG: sleeping function called from invalid context at mm/slab.h:422
>
> Nov 3 20:24:11 turing-police kernel: [ 60.093793] BUG: sleeping function called from invalid context at mm/slab.h:422
> Nov 4 20:20:54 turing-police kernel: [86264.366955] BUG: sleeping function called from invalid context at mm/slab.h:422
> Nov 5 19:17:40 turing-police kernel: [172469.769179] BUG: sleeping function called from invalid context at mm/slab.h:422
> Nov 6 06:07:37 turing-police kernel: [211467.239460] BUG: sleeping function called from invalid context at mm/slab.h:422
>
> Nov 6 14:12:43 turing-police kernel: [ 54.891848] BUG: sleeping function called from invalid context at mm/slab.h:422
>
> Something seems to be going astray while handling a RA packet.
Odd. I tested RA before sending the patches and again just now - no
traceback with an RCU / lock debugging kernel. What is sending the RA's
in your case? I'd like to understand the config and add a test for this.
Powered by blists - more mailing lists