From: Christoph Hellwig <hch@lst.de>
To: syzbot <syzbot+53369d11851d8f26735c@syzkaller.appspotmail.com>
Cc: 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: Mon, 12 Jun 2023 05:30:23 +0200 [thread overview]
Message-ID: <20230612033023.GA16241@lst.de> (raw)
In-Reply-To: <000000000000c0951105fde12435@google.com>
On Sun, Jun 11, 2023 at 02:18:29PM -0700, syzbot wrote:
> 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
I can't see how that btrfs commit would affect nilfs2..
next prev parent reply other threads:[~2023-06-12 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000da4f6b05eb9bf593@google.com>
2023-06-11 3:56 ` [syzbot] [nilfs?] general protection fault in nilfs_clear_dirty_page syzbot
2023-06-11 21:18 ` syzbot
2023-06-12 3:30 ` Christoph Hellwig [this message]
2023-06-12 3:59 ` Ryusuke Konishi
2023-06-12 2:14 ` [PATCH] nilfs2: prevent general protection fault in nilfs_clear_dirty_page() 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=20230612033023.GA16241@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dsterba@suse.com \
--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=syzbot+53369d11851d8f26735c@syzkaller.appspotmail.com \
--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).