On Fri, Aug 16, 2024 at 06:43:38PM GMT, Aleksandr Nogikh wrote: > On Fri, Aug 16, 2024 at 6:30 PM Kent Overstreet > <kent.overstr...@linux.dev> wrote: > > > > On Fri, Aug 16, 2024 at 02:50:23AM GMT, syzbot wrote: > > > Hello, > > > > > > syzbot found the following issue on: > > > > > > HEAD commit: d7a5aa4b3c00 Merge tag > > > 'perf-tools-fixes-for-v6.11-2024-08.. > > > git tree: upstream > > > console output: https://syzkaller.appspot.com/x/log.txt?x=131e27c5980000 > > > kernel config: https://syzkaller.appspot.com/x/.config?x=7229118d88b4a71b > > > dashboard link: > > > https://syzkaller.appspot.com/bug?extid=95e40eae71609e40d851 > > > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for > > > Debian) 2.40 > > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150be3c5980000 > > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165c93cb980000 > > > > > > Downloadable assets: > > > disk image (non-bootable): > > > https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-d7a5aa4b.raw.xz > > > vmlinux: > > > https://storage.googleapis.com/syzbot-assets/af15738cca6c/vmlinux-d7a5aa4b.xz > > > kernel image: > > > https://storage.googleapis.com/syzbot-assets/62dacb1384ee/bzImage-d7a5aa4b.xz > > > mounted in repro: > > > https://storage.googleapis.com/syzbot-assets/92de1b01cc1a/mount_0.gz > > > > > > IMPORTANT: if you fix the issue, please add the following tag to the > > > commit: > > > Reported-by: syzbot+95e40eae71609e40d...@syzkaller.appspotmail.com > > > > > > R13: 00007f7d2a233210 R14: 0000000000000001 R15: 0032656c69662f2e > > > </TASK> > > > > Dmitry, this bug has been fixed upstream, and I've been seeing others > > where syzbot appears to be generating reports for bugs that have been > > fixed (e.g. BUG() in bch2_fs_journal_stop() long after that was changed > > to a warning). > > > > I don't know what's going on, but the report appears to be in error. > > Did those fixes already reach the latest torvalds? > I've just tried to run the C reproducer from the report on > d7a5aa4b3c00 several times and it eventually did crash the kernel. > > [ 42.746251][ T5239] ------------[ cut here ]------------ > [ 42.747210][ T5239] WARNING: CPU: 0 PID: 5239 at fs/inode.c:1143 > discard_new_inode+0x217/0x2a0 > [ 42.748401][ T5239] Modules linked in: > [ 42.748948][ T5239] CPU: 0 UID: 0 PID: 5239 Comm: repro Not tainted > 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 > [ 42.750331][ T5239] Hardware name: QEMU Standard PC (Q35 + ICH9, > 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 > [ 42.751806][ T5239] RIP: 0010:discard_new_inode+0x217/0x2a0
found it, i_state != i_flags - sorry to bother you guys :)
