From: syzbot <syzbot+5f682cd029581f9edfd1@syzkaller.appspotmail.com>
To: VEfanov@ispras.ru, jack@suse.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vefanov@ispras.ru
Subject: [syzbot] [udf?] kernel BUG in submit_bh_wbc (2)
Date: Thu, 25 Apr 2024 02:05:31 -0700 [thread overview]
Message-ID: <000000000000d006b20616e8168d@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e88c4cfcb7b8 Merge tag 'for-6.9-rc5-tag' of git://git.kern..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10288be8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5a05c230e142f2bc
dashboard link: https://syzkaller.appspot.com/bug?extid=5f682cd029581f9edfd1
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=10e4cd6b180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f27380980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/124765f3f2cd/disk-e88c4cfc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0e2773bfa348/vmlinux-e88c4cfc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/66c56fe803c8/bzImage-e88c4cfc.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a47950266a82/mount_0.gz
The issue was bisected to:
commit 1e0d4adf17e7ef03281d7b16555e7c1508c8ed2d
Author: Vladislav Efanov <VEfanov@ispras.ru>
Date: Thu Feb 2 14:04:56 2023 +0000
udf: Check consistency of Space Bitmap Descriptor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155c96a0980000
final oops: https://syzkaller.appspot.com/x/report.txt?x=175c96a0980000
console output: https://syzkaller.appspot.com/x/log.txt?x=135c96a0980000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5f682cd029581f9edfd1@syzkaller.appspotmail.com
Fixes: 1e0d4adf17e7 ("udf: Check consistency of Space Bitmap Descriptor")
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
------------[ cut here ]------------
kernel BUG at fs/buffer.c:2768!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 PID: 5075 Comm: syz-executor330 Not tainted 6.9.0-rc5-syzkaller-00042-ge88c4cfcb7b8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:submit_bh_wbc+0x546/0x560 fs/buffer.c:2768
Code: 04 7c ff be 00 10 00 00 48 c7 c7 80 ad 47 8e 4c 89 fa e8 1d 33 c6 02 e9 95 fe ff ff e8 93 04 7c ff 90 0f 0b e8 8b 04 7c ff 90 <0f> 0b e8 83 04 7c ff 90 0f 0b e8 7b 04 7c ff 90 0f 0b e8 73 04 7c
RSP: 0018:ffffc9000340f858 EFLAGS: 00010293
RAX: ffffffff8219fbe5 RBX: 0000000000000000 RCX: ffff88802f7b9e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff8219f743 R09: 1ffff1100ee296cb
R10: dffffc0000000000 R11: ffffed100ee296cc R12: 0000000000000000
R13: ffff88807714b658 R14: 0000000000000000 R15: 1ffff1100ee296cb
FS: 00005555792e0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000066c7e0 CR3: 0000000075a64000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
submit_bh fs/buffer.c:2809 [inline]
__bh_read fs/buffer.c:3074 [inline]
bh_read_nowait include/linux/buffer_head.h:417 [inline]
__block_write_begin_int+0x12d0/0x1a70 fs/buffer.c:2134
__block_write_begin fs/buffer.c:2154 [inline]
block_write_begin+0x9b/0x1e0 fs/buffer.c:2213
udf_write_begin+0x10d/0x1a0 fs/udf/inode.c:261
generic_perform_write+0x322/0x640 mm/filemap.c:3974
udf_file_write_iter+0x2fd/0x660 fs/udf/file.c:111
call_write_iter include/linux/fs.h:2110 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0xa84/0xcb0 fs/read_write.c:590
ksys_write+0x1a0/0x2c0 fs/read_write.c:643
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7c2bb82679
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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:00007fff23ee0518 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fff23ee06e8 RCX: 00007f7c2bb82679
RDX: 0000000000000010 RSI: 0000000020000600 RDI: 0000000000000004
RBP: 00007f7c2bbf5610 R08: 00007fff23ee06e8 R09: 00007fff23ee06e8
R10: 00007fff23ee06e8 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff23ee06d8 R14: 0000000000000001 R15: 0000000000000001
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:submit_bh_wbc+0x546/0x560 fs/buffer.c:2768
Code: 04 7c ff be 00 10 00 00 48 c7 c7 80 ad 47 8e 4c 89 fa e8 1d 33 c6 02 e9 95 fe ff ff e8 93 04 7c ff 90 0f 0b e8 8b 04 7c ff 90 <0f> 0b e8 83 04 7c ff 90 0f 0b e8 7b 04 7c ff 90 0f 0b e8 73 04 7c
RSP: 0018:ffffc9000340f858 EFLAGS: 00010293
RAX: ffffffff8219fbe5 RBX: 0000000000000000 RCX: ffff88802f7b9e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff8219f743 R09: 1ffff1100ee296cb
R10: dffffc0000000000 R11: ffffed100ee296cc R12: 0000000000000000
R13: ffff88807714b658 R14: 0000000000000000 R15: 1ffff1100ee296cb
FS: 00005555792e0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000066c7e0 CR3: 0000000075a64000 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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If the report is already addressed, 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 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
reply other threads:[~2024-04-25 9:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000d006b20616e8168d@google.com \
--to=syzbot+5f682cd029581f9edfd1@syzkaller.appspotmail.com \
--cc=VEfanov@ispras.ru \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.