From: syzbot <syzbot+53369d11851d8f26735c@syzkaller.appspotmail.com>
To: axboe@kernel.dk, dsterba@suse.com, hch@lst.de,
konishi.ryusuke@gmail.com, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wqu@suse.com
Subject: Re: [syzbot] [nilfs?] general protection fault in nilfs_clear_dirty_page
Date: Sun, 11 Jun 2023 14:18:29 -0700 [thread overview]
Message-ID: <000000000000c0951105fde12435@google.com> (raw)
In-Reply-To: <000000000000da4f6b05eb9bf593@google.com>
syzbot has bisected this issue to:
commit 4a445b7b6178d88956192c0202463063f52e8667
Author: Qu Wenruo <wqu@suse.com>
Date: Sat Aug 13 08:06:53 2022 +0000
btrfs: don't merge pages into bio if their page offset is not contiguous
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17778475280000
start commit: 022ce8862dff Merge tag 'i2c-for-6.4-rc6' of git://git.kern..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f78475280000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f78475280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7474de833c217bf4
dashboard link: https://syzkaller.appspot.com/bug?extid=53369d11851d8f26735c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e9d48b280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d7fa63280000
Reported-by: syzbot+53369d11851d8f26735c@syzkaller.appspotmail.com
Fixes: 4a445b7b6178 ("btrfs: don't merge pages into bio if their page offset is not contiguous")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-11 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 9:12 [syzbot] general protection fault in nilfs_clear_dirty_page syzbot
[not found] ` <000000000000da4f6b05eb9bf593-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-06-11 3:56 ` [syzbot] [nilfs?] " syzbot
2023-06-12 2:14 ` [PATCH] nilfs2: prevent general protection fault in nilfs_clear_dirty_page() Ryusuke Konishi
2023-06-11 21:18 ` syzbot [this message]
[not found] ` <000000000000c0951105fde12435-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-06-12 3:30 ` [syzbot] [nilfs?] general protection fault in nilfs_clear_dirty_page Christoph Hellwig
[not found] ` <20230612033023.GA16241-jcswGhMUV9g@public.gmane.org>
2023-06-12 3:59 ` Ryusuke Konishi
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=000000000000c0951105fde12435@google.com \
--to=syzbot+53369d11851d8f26735c@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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;
as well as URLs for NNTP newsgroup(s).