From: Al Viro <viro@ZenIV.linux.org.uk>
To: syzbot <syzbot+f3bd89a5ab3266b10540@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: corrupted list in __dentry_kill
Date: Sun, 1 Apr 2018 21:05:31 +0100 [thread overview]
Message-ID: <20180401200531.GA30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180401033519.GZ30522@ZenIV.linux.org.uk>
On Sun, Apr 01, 2018 at 04:35:19AM +0100, Al Viro wrote:
> On Sat, Mar 31, 2018 at 04:01:02PM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot hit the following crash on bpf-next commit
> > 7828f20e3779e4e85e55371e0e43f5006a15fb41 (Sat Mar 31 00:17:57 2018 +0000)
> > Merge branch 'bpf-cgroup-bind-connect'
> > syzbot dashboard link:
> > https://syzkaller.appspot.com/bug?extid=f3bd89a5ab3266b10540
> >
> > So far this crash happened 22 times on bpf-next, upstream.
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6290970458980352
> > syzkaller reproducer:
> > https://syzkaller.appspot.com/x/repro.syz?id=6577156880596992
> > Raw console output:
> > https://syzkaller.appspot.com/x/log.txt?id=5107570603720704
> > Kernel config:
> > https://syzkaller.appspot.com/x/.config?id=5909223872832634926
> > compiler: gcc (GCC) 7.1.1 20170620
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+f3bd89a5ab3266b10540@syzkaller.appspotmail.com
> > It will help syzbot understand when the bug is fixed. See footer for
> > details.
> > If you forward the report, please keep this part and the footer.
> >
> > RBP: 00007ffd1bbb3ae0 R08: 0000000020000200 R09: 0000000300000000
> > R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffff
> > R13: 0000000000000003 R14: 0000000000001380 R15: 00007ffd1bbb3378
> > list_del corruption. prev->next should be 00000000a8104008, but was
> > 00000000081c6144
>
> Lovely... I'll look into that tomorrow morning.
Can't reproduce - it reproducer had been running for several hours, with
that kernel and that config (gcc 6.3, not 7.1, though), no oopsen...
If somebody can reproduce that thing, I'd appreciate having it bisected
a bit...
next prev parent reply other threads:[~2018-04-01 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 23:01 BUG: corrupted list in __dentry_kill syzbot
2018-04-01 3:35 ` Al Viro
2018-04-01 20:05 ` Al Viro [this message]
2018-04-01 21:05 ` Eric Biggers
2018-04-01 21:48 ` Eric Biggers
2018-04-01 22:20 ` Matthew Wilcox
2018-04-02 6:44 ` Al Viro
2018-04-02 20:37 ` Al Viro
2018-04-20 2:20 ` Eric Biggers
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=20180401200531.GA30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+f3bd89a5ab3266b10540@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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