linux-kernel - Re: [syzbot] [fs?] kernel BUG in submit_bh

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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKFNMomwgmzwxbRKtDvbK-N0wWJ8iY9Xg-c_mBKzC3W90pXUMg@mail.gmail.com>
Date: Mon, 14 Oct 2024 18:53:33 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: syzbot <syzbot+985ada84bf055a575c07@...kaller.appspotmail.com>
Cc: syzkaller-bugs@...glegroups.com, linux-nilfs@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [syzbot] [fs?] kernel BUG in submit_bh_wbc (3)

On Mon, Oct 14, 2024 at 3:02 PM syzbot
<syzbot+985ada84bf055a575c07@...kaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    6485cf5ea253 Merge tag 'hid-for-linus-2024101301' of git:/..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=142f585f980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=164d2822debd8b0d
> dashboard link: https://syzkaller.appspot.com/bug?extid=985ada84bf055a575c07
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/f39f2ba63ff0/disk-6485cf5e.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/1b68f3c352ce/vmlinux-6485cf5e.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/38070176e828/bzImage-6485cf5e.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+985ada84bf055a575c07@...kaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/buffer.c:2785!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
> CPU: 0 UID: 0 PID: 5968 Comm: syz.0.65 Not tainted 6.12.0-rc3-syzkaller-00007-g6485cf5ea253 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
> RIP: 0010:submit_bh_wbc+0x556/0x560 fs/buffer.c:2785
> Code: 89 fa e8 dd d7 cb 02 e9 95 fe ff ff e8 63 9b 74 ff 90 0f 0b e8 5b 9b 74 ff 90 0f 0b e8 53 9b 74 ff 90 0f 0b e8 4b 9b 74 ff 90 <0f> 0b e8 43 9b 74 ff 90 0f 0b 90 90 90 90 90 90 90 90 90 90 90 90
> RSP: 0018:ffffc9000303e9f8 EFLAGS: 00010287
> RAX: ffffffff82204bb5 RBX: 0000000000000154 RCX: 0000000000040000
> RDX: ffffc900044b1000 RSI: 0000000000000a81 RDI: 0000000000000a82
> RBP: 0000000000000100 R08: ffffffff82204779 R09: 1ffff1100ae83f79
> R10: dffffc0000000000 R11: ffffed100ae83f7a R12: 0000000000000000
> R13: ffff88805741fbc8 R14: 0000000000000000 R15: 1ffff1100ae83f79
> FS:  00007fbfb2dcc6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f08b6361160 CR3: 000000005f354000 CR4: 00000000003526f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <TASK>
>  submit_bh fs/buffer.c:2824 [inline]
>  block_read_full_folio+0x93b/0xcd0 fs/buffer.c:2451
>  do_mpage_readpage+0x1a73/0x1c80 fs/mpage.c:317
>  mpage_read_folio+0x108/0x1e0 fs/mpage.c:392
>  filemap_read_folio+0x14b/0x630 mm/filemap.c:2367
>  do_read_cache_folio+0x3f5/0x850 mm/filemap.c:3825
>  read_mapping_folio include/linux/pagemap.h:1011 [inline]
>  nilfs_get_folio+0x4b/0x240 fs/nilfs2/dir.c:190
>  nilfs_find_entry+0x138/0x650 fs/nilfs2/dir.c:313
>  nilfs_inode_by_name+0xa8/0x210 fs/nilfs2/dir.c:393
>  nilfs_lookup+0x76/0x110 fs/nilfs2/namei.c:62
>  __lookup_slow+0x28c/0x3f0 fs/namei.c:1732
>  lookup_slow fs/namei.c:1749 [inline]
>  lookup_one_unlocked+0x1a4/0x290 fs/namei.c:2912
>  ovl_lookup_positive_unlocked fs/overlayfs/namei.c:210 [inline]
>  ovl_lookup_single+0x200/0xbd0 fs/overlayfs/namei.c:240
>  ovl_lookup_layer+0x417/0x510 fs/overlayfs/namei.c:333
>  ovl_lookup+0x5d8/0x2a60 fs/overlayfs/namei.c:1068
>  lookup_open fs/namei.c:3573 [inline]
>  open_last_lookups fs/namei.c:3694 [inline]
>  path_openat+0x11a7/0x3590 fs/namei.c:3930
>  do_filp_open+0x235/0x490 fs/namei.c:3960
>  do_sys_openat2+0x13e/0x1d0 fs/open.c:1415
>  do_sys_open fs/open.c:1430 [inline]
>  __do_sys_open fs/open.c:1438 [inline]
>  __se_sys_open fs/open.c:1434 [inline]
>  __x64_sys_open+0x225/0x270 fs/open.c:1434
>  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
>  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fbfb1f7dff9
> Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fbfb2dcc038 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
> RAX: ffffffffffffffda RBX: 00007fbfb2135f80 RCX: 00007fbfb1f7dff9
> RDX: 0000000000000000 RSI: 000000000014d27e RDI: 0000000020000180
> RBP: 00007fbfb1ff0296 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 0000000000000000 R14: 00007fbfb2135f80 R15: 00007ffe859206a8
>  </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:submit_bh_wbc+0x556/0x560 fs/buffer.c:2785
> Code: 89 fa e8 dd d7 cb 02 e9 95 fe ff ff e8 63 9b 74 ff 90 0f 0b e8 5b 9b 74 ff 90 0f 0b e8 53 9b 74 ff 90 0f 0b e8 4b 9b 74 ff 90 <0f> 0b e8 43 9b 74 ff 90 0f 0b 90 90 90 90 90 90 90 90 90 90 90 90
> RSP: 0018:ffffc9000303e9f8 EFLAGS: 00010287
> RAX: ffffffff82204bb5 RBX: 0000000000000154 RCX: 0000000000040000
> RDX: ffffc900044b1000 RSI: 0000000000000a81 RDI: 0000000000000a82
> RBP: 0000000000000100 R08: ffffffff82204779 R09: 1ffff1100ae83f79
> R10: dffffc0000000000 R11: ffffed100ae83f7a R12: 0000000000000000
> R13: ffff88805741fbc8 R14: 0000000000000000 R15: 1ffff1100ae83f79
> FS:  00007fbfb2dcc6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f08b6361160 CR3: 000000005f354000 CR4: 00000000003526f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@...glegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
>
> If you want to overwrite report's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
>
> If the report is a duplicate of another one, reply with:
> #syz dup: exact-subject-of-another-report
>
> If you want to undo deduplication, reply with:
> #syz undup

I can't say for sure, but from the stack trace, this seems to be an
issue with nilfs2, so I'll add the nilfs tag:

#syz set subsystems: nilfs, fs

Ryusuke Konishi