linux-kernel - Re: [syzbot] [nilfs?] kernel BUG in folio_end

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKFNMo=XRe5UZeOEumfTJYRndDb0YrxhO=9261jq4aRNaPqXYg@mail.gmail.com>
Date:   Tue, 22 Aug 2023 01:47:38 +0900
From:   Ryusuke Konishi <konishi.ryusuke@...il.com>
To:     syzbot <syzbot+7e5cf1d80677ec185e63@...kaller.appspotmail.com>
Cc:     akpm@...ux-foundation.org, brauner@...nel.org,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, linux-nilfs@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk,
        willy@...radead.org
Subject: Re: [syzbot] [nilfs?] kernel BUG in folio_end_writeback

On Mon, Aug 21, 2023 at 3:41 AM syzbot
<syzbot+7e5cf1d80677ec185e63@...kaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 92c5d1b860e9581d64baca76779576c0ab0d943d
> Author: Ryusuke Konishi <konishi.ryusuke@...il.com>
> Date:   Fri May 26 02:13:32 2023 +0000
>
>     nilfs2: reject devices with insufficient block count
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=170c6337a80000
> start commit:   929ed21dfdb6 Merge tag '6.4-rc4-smb3-client-fixes' of git:..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=3da6c5d3e0a6c932
> dashboard link: https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16cb3b69280000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10f34201280000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: nilfs2: reject devices with insufficient block count
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

I have confirmed that one of the five registered reproducers emits the
error message that is output when the above commit takes effect.
However, the remaining four did not.
So, I think it's premature to conclude that the issue has been fixed
by this commit at this time.

Ryusuke Konishi