Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 12 Jun 2023 05:30:23 +0200
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
Message-ID: <20230612033023.GA16241@lst.de>
References: <000000000000da4f6b05eb9bf593@google.com> <000000000000c0951105fde12435@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000000000000c0951105fde12435@google.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Precedence: bulk

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..