linux-kernel - Re: [syzbot] [ntfs3?] BUG: unable to handle kernel paging request in step

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: <20240214094555.bcmnrnae3jndqjez@quack3>
Date: Wed, 14 Feb 2024 10:45:55 +0100
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+0994679b6f098bb3da6d@...kaller.appspotmail.com>
Cc: almaz.alexandrovich@...agon-software.com, anton@...era.com,
	axboe@...nel.dk, brauner@...nel.org, jack@...e.cz,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-ntfs-dev@...ts.sourceforge.net, ntfs3@...ts.linux.dev,
	syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel paging request in
 step_into

On Tue 13-02-24 10:42:03, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@...e.cz>
> Date:   Wed Nov 1 17:43:10 2023 +0000
> 
>     fs: Block writes to mounted block devices
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10656c42180000
> start commit:   bff687b3dad6 Merge tag 'block-6.2-2022-12-29' of git://git..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=68e0be42c8ee4bb4
> dashboard link: https://syzkaller.appspot.com/bug?extid=0994679b6f098bb3da6d
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11307974480000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15c567f2480000
> 
> If the result looks correct, please mark the issue as fixed by replying with:
> 
> #syz fix: fs: Block writes to mounted block devices

There seem to be other reproducers which keep working and they don't seem
to be doing anything with the device. So I don't think this is really
fixing it.

								Honza

-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR