[v5.15] kernel BUG in submit_bh_wbc

1 view
Skip to first unread message

syzbot

unread,
Jun 4, 2023, 4:30:06 PM6/4/23
Hello,

syzbot found the following issue on:

HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1087f8c9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=2d24dbde73b9b505
dashboard link: https://syzkaller.appspot.com/bug?extid=2a8a79e5f46dc7539f3e
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137212a5280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14943379280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/48a0cd4fb454/disk-0ab06468.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d857ea64526d/vmlinux-0ab06468.xz
kernel image: https://storage.googleapis.com/syzbot-assets/330499c124c4/bzImage-0ab06468.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4b2bc10b3b73/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

NILFS (loop0): nilfs_get_block (ino=19): a race condition while inserting a data block at offset=0
------------[ cut here ]------------
kernel BUG at fs/buffer.c:3017!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3563 Comm: syz-executor343 Not tainted 5.15.114-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:submit_bh_wbc+0x66d/0x690 fs/buffer.c:3017
Code: 8b 0c 24 80 e1 07 fe c1 38 c1 0f 8c a8 fc ff ff 48 8b 3c 24 e8 e4 43 e4 ff e9 9a fc ff ff e8 ea e8 9a ff 0f 0b e8 e3 e8 9a ff <0f> 0b e8 dc e8 9a ff 0f 0b e8 d5 e8 9a ff 0f 0b e8 ce e8 9a ff 0f
RSP: 0018:ffffc90002eff7b0 EFLAGS: 00010293
RAX: ffffffff81e5106d RBX: 0000000000000000 RCX: ffff88801e3e9dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81e50aa6 R09: ffffed100e08ad23
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff888070456910 R15: 0000000000000000
FS: 00007fa1b8204700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa1c0526000 CR3: 000000001b33b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ll_rw_block+0x1cf/0x230
__block_write_begin_int+0xdb4/0x1650 fs/buffer.c:2042
__block_write_begin fs/buffer.c:2062 [inline]
block_write_begin+0x4f/0xc0 fs/buffer.c:2122
nilfs_write_begin+0xa6/0x120 fs/nilfs2/inode.c:263
generic_perform_write+0x2bf/0x5b0 mm/filemap.c:3776
__generic_file_write_iter+0x381/0x4f0 mm/filemap.c:3871
generic_file_write_iter+0xa7/0x1b0 mm/filemap.c:3935
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fa1c05796e9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa1b82042f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fa1c05ff7b0 RCX: 00007fa1c05796e9
RDX: 00000000000000a0 RSI: 0000000020000380 RDI: 0000000000000006
RBP: 00007fa1c05cbd1c R08: 00000000ffffff7f R09: 0000000000000000
R10: 000000000000001b R11: 0000000000000246 R12: 00007fa1c05cbb18
R13: 3f00000000000000 R14: 0400000000000000 R15: 00007fa1c05ff7b8
</TASK>
Modules linked in:
---[ end trace f219f70bc2292857 ]---
RIP: 0010:submit_bh_wbc+0x66d/0x690 fs/buffer.c:3017
Code: 8b 0c 24 80 e1 07 fe c1 38 c1 0f 8c a8 fc ff ff 48 8b 3c 24 e8 e4 43 e4 ff e9 9a fc ff ff e8 ea e8 9a ff 0f 0b e8 e3 e8 9a ff <0f> 0b e8 dc e8 9a ff 0f 0b e8 d5 e8 9a ff 0f 0b e8 ce e8 9a ff 0f
RSP: 0018:ffffc90002eff7b0 EFLAGS: 00010293
RAX: ffffffff81e5106d RBX: 0000000000000000 RCX: ffff88801e3e9dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81e50aa6 R09: ffffed100e08ad23
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff888070456910 R15: 0000000000000000
FS: 00007fa1b8204700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa1c05badc0 CR3: 000000001b33b000 CR4: 00000000003506f0
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 [email protected].

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jun 16, 2024, 5:58:13 PM6/16/24
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages