From: Bart Van Assche <bvanassche@acm.org>
To: jaegeuk@kernel.org
Cc: axboe@kernel.dk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: kernel BUG at fs/buffer.c:LINE!
Date: Wed, 18 Dec 2019 21:00:21 -0800 [thread overview]
Message-ID: <31033055-c245-4eda-2814-3fd8b0d59cb9@acm.org> (raw)
In-Reply-To: <0000000000009716290599fcd496@google.com>
On 2019-12-18 08:21, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 5db470e229e22b7eda6e23b5566e532c96fb5bc3
> Author: Jaegeuk Kim <jaegeuk@kernel.org>
> Date: Thu Jan 10 03:17:14 2019 +0000
>
> loop: drop caches if offset or block_size are changed
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f3ca8ee00000
> start commit: 2187f215 Merge tag 'for-5.5-rc2-tag' of
> git://git.kernel.o..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=100bca8ee00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17f3ca8ee00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=dcf10bf83926432a
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1171ba8ee00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=107440aee00000
Hi Jaegeuk,
Since syzbot has identified a reproducer I think that it's easy to test
whether your new patch fixes what syzbot discovered. Have you already
had the chance to test this?
Thanks,
Bart.
next prev parent reply other threads:[~2019-12-19 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 16:02 kernel BUG at fs/buffer.c:LINE! syzbot
2019-12-18 11:36 ` syzbot
2019-12-18 16:21 ` syzbot
2019-12-19 5:00 ` Bart Van Assche [this message]
2019-12-19 19:15 ` Jaegeuk Kim
2019-12-19 23:30 ` Jaegeuk Kim
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=31033055-c245-4eda-2814-3fd8b0d59cb9@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).