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;
MIME-Version: 1.0
References: <000000000000da4f6b05eb9bf593@google.com> <000000000000c0951105fde12435@google.com>
 <20230612033023.GA16241@lst.de>
In-Reply-To: <20230612033023.GA16241@lst.de>
From:   Ryusuke Konishi <konishi.ryusuke@gmail.com>
Date:   Mon, 12 Jun 2023 12:59:39 +0900
Message-ID: <CAKFNMomCUnaB3_3chQm4P8devx2NwAp2hMpYfbyaHKyO2WLEkw@mail.gmail.com>
Subject: Re: [syzbot] [nilfs?] general protection fault in nilfs_clear_dirty_page
To:     Christoph Hellwig <hch@lst.de>
Cc:     syzbot <syzbot+53369d11851d8f26735c@syzkaller.appspotmail.com>,
        axboe@kernel.dk, dsterba@suse.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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Jun 12, 2023 at 12:30=E2=80=AFPM Christoph Hellwig wrote:
>
> 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 conti=
guous
>
> I can't see how that btrfs commit would affect nilfs2..

Yeah, I think this bisection result is wrong.
I have already posted a bug-fix patch titled "nilfs2: prevent general
protection fault in nilfs_clear_dirty_page()"
for this issue.

Thanks,
Ryusuke Konishi