From: David Ahern <dsahern@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Valdis Kletnieks <valdis.kletnieks@vt.edu>,
"David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 issue in next-20171102 - lockdep and BUG handling RA packet.
Date: Tue, 7 Nov 2017 09:39:08 +0900 [thread overview]
Message-ID: <251dd152-68dc-2d26-5207-45376fa5203b@gmail.com> (raw)
In-Reply-To: <CANn89iKyFsMQ+=2Vj7ErTBk_xC+sB9XuU2UQqM_u7LmOGHcRfw@mail.gmail.com>
On 11/7/17 9:31 AM, Eric Dumazet wrote:
> On Mon, Nov 6, 2017 at 4:29 PM, David Ahern <dsahern@gmail.com> wrote:
>> On 11/7/17 5:56 AM, valdis.kletnieks@vt.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.
>
> Do you have CONFIG_DEBUG_ATOMIC_SLEEP=y in your .config ?
>
I needed to set sysctl -w net.ipv6.conf.eth1.use_tempaddr=1. With that I
see the trace.
prev parent reply other threads:[~2017-11-07 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 20:56 IPv6 issue in next-20171102 - lockdep and BUG handling RA packet valdis.kletnieks
2017-11-06 22:01 ` Ido Schimmel
2017-11-06 22:04 ` Eric Dumazet
2017-11-06 22:15 ` Eric Dumazet
2017-11-07 0:29 ` David Ahern
2017-11-07 0:31 ` Eric Dumazet
2017-11-07 0:33 ` David Ahern
2017-11-07 0:39 ` David Ahern [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=251dd152-68dc-2d26-5207-45376fa5203b@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).