From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+ea7d9cb314b4ab49a18a@syzkaller.appspotmail.com>
Cc: David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: INFO: rcu detected stall in ndisc_alloc_skb
Date: Mon, 31 Dec 2018 17:17:17 +0900 [thread overview]
Message-ID: <ef2508c9-d069-2143-09a6-a90b9ef12568@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CACT4Y+Yx4BJw=F_PMx9a8AjPKzEwhzLnzt9K-dgkBoNkKQj2+g@mail.gmail.com>
On 2018/12/31 16:49, Dmitry Vyukov wrote:
> On Mon, Dec 31, 2018 at 8:42 AM syzbot
> <syzbot+ea7d9cb314b4ab49a18a@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: ef4ab8447aa2 selftests: bpf: install script with_addr.sh
>> git tree: bpf-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=14a28b6e400000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=7e7e2279c0020d5f
>> dashboard link: https://syzkaller.appspot.com/bug?extid=ea7d9cb314b4ab49a18a
>> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>>
>> Unfortunately, I don't have any reproducer for this crash yet.
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+ea7d9cb314b4ab49a18a@syzkaller.appspotmail.com
>
> Since this involves OOMs and looks like a one-off induced memory corruption:
>
> #syz dup: kernel panic: corrupted stack end in wb_workfn
>
Why?
RCU stall in this case is likely to be latency caused by flooding of printk().
next prev parent reply other threads:[~2018-12-31 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 7:42 INFO: rcu detected stall in ndisc_alloc_skb syzbot
2018-12-31 7:49 ` Dmitry Vyukov
2018-12-31 8:17 ` Tetsuo Handa [this message]
2018-12-31 8:24 ` Dmitry Vyukov
2019-01-02 17:06 ` Tetsuo Handa
2019-01-05 10:49 ` Tetsuo Handa
2019-01-06 13:24 ` Dmitry Vyukov
2019-01-06 13:47 ` Tetsuo Handa
2019-01-07 11:12 ` Dmitry Vyukov
2019-01-18 5:20 ` Tetsuo Handa
2019-01-19 12:16 ` Dmitry Vyukov
2019-01-19 13:10 ` Tetsuo Handa
2019-01-20 13:30 ` Dmitry Vyukov
2019-01-20 14:24 ` Tetsuo Handa
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=ef2508c9-d069-2143-09a6-a90b9ef12568@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+ea7d9cb314b4ab49a18a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/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).