From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+31043da7725b6ec210f1@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 (2)
Date: Thu, 12 Dec 2019 06:12:06 +0000 [thread overview]
Message-ID: <20191212061206.GE4203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <000000000000b6b03205997b71cf@google.com>
On Wed, Dec 11, 2019 at 09:59:11PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 938f49c8 Add linux-next specific files for 20191211
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=150eba1ee00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=96834c884ba7bb81
> dashboard link: https://syzkaller.appspot.com/bug?extid=31043da7725b6ec210f1
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12dc83dae00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ac8396e00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+31043da7725b6ec210f1@syzkaller.appspotmail.com
Already fixed in a3d1e7eb5abe3aa1095bc75d1a6760d3809bd672
next prev parent reply other threads:[~2019-12-12 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 5:59 BUG: corrupted list in __dentry_kill (2) syzbot
2019-12-12 6:12 ` Al Viro [this message]
2019-12-12 6:48 ` Dmitry Vyukov
2019-12-12 13:38 ` Al Viro
2019-12-12 15:57 ` Dmitry Vyukov
2019-12-12 18:34 ` Al Viro
2019-12-13 9:10 ` Dmitry Vyukov
2019-12-12 11:35 ` syzbot
2019-12-12 11:35 ` syzbot
2019-12-12 11:35 ` syzbot
2019-12-12 11:35 ` [Bridge] " syzbot
[not found] <20191212104355.24672-1-hdanton@sina.com>
2019-12-12 13:14 ` Al Viro
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=20191212061206.GE4203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+31043da7725b6ec210f1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.