From: syzbot <syzbot+64f520f6fe02b8947407@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] [ext4?] kernel BUG in ext4_mb_release_inode_pa
Date: Sat, 25 Nov 2023 02:34:20 -0800 [thread overview]
Message-ID: <0000000000009800de060af79c8f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 98b1cc82c4af Linux 6.7-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11583b58e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=aec35c1281ec0aaf
dashboard link: https://syzkaller.appspot.com/bug?extid=64f520f6fe02b8947407
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163a9768e80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b60687e82ad4/disk-98b1cc82.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/29477f0b04df/vmlinux-98b1cc82.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9aab12888a60/bzImage-98b1cc82.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9009db42dccd/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+64f520f6fe02b8947407@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/ext4/mballoc.c:5300!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 10719 Comm: syz-executor.1 Not tainted 6.7.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:ext4_mb_release_inode_pa.isra.0+0xa30/0xb80 fs/ext4/mballoc.c:5300
Code: b5 fb ff ff e8 a1 1a 50 ff 90 0f 0b e8 99 1a 50 ff 31 ff 44 89 ee e8 ff 15 50 ff 45 85 ed 0f 84 81 f8 ff ff e8 81 1a 50 ff 90 <0f> 0b e8 69 e7 a5 ff e9 e5 f6 ff ff 48 89 d7 e8 5c e7 a5 ff e9 4a
RSP: 0018:ffffc9000a1af690 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000ffffe428 RCX: ffffffff823665c1
RDX: ffff88802b52a1c0 RSI: ffffffff823665cf RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000005 R12: ffff88806442ac08
R13: 0000000000000002 R14: 1ffff92001435ee1 R15: ffff88806440c868
FS: 00007fbecfbfe6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020027040 CR3: 000000007c40e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_discard_preallocations+0x796/0xfb0 fs/ext4/mballoc.c:5581
ext4_truncate+0xd27/0x1310 fs/ext4/inode.c:4166
ext4_truncate_failed_write fs/ext4/truncate.h:22 [inline]
ext4_write_end+0xa8a/0xed0 fs/ext4/inode.c:1323
ext4_da_write_end+0x926/0x1170 fs/ext4/inode.c:3019
generic_perform_write+0x32f/0x600 mm/filemap.c:3929
ext4_buffered_write_iter+0x11f/0x3c0 fs/ext4/file.c:299
ext4_file_write_iter+0x819/0x1950 fs/ext4/file.c:696
call_write_iter include/linux/fs.h:2020 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x64f/0xdf0 fs/read_write.c:584
ksys_write+0x12f/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fbed087cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbecfbfe0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fbed099bf80 RCX: 00007fbed087cae9
RDX: 000000000208e24b RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00007fbed08c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fbed099bf80 R15: 00007ffd459e66e8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_mb_release_inode_pa.isra.0+0xa30/0xb80 fs/ext4/mballoc.c:5300
Code: b5 fb ff ff e8 a1 1a 50 ff 90 0f 0b e8 99 1a 50 ff 31 ff 44 89 ee e8 ff 15 50 ff 45 85 ed 0f 84 81 f8 ff ff e8 81 1a 50 ff 90 <0f> 0b e8 69 e7 a5 ff e9 e5 f6 ff ff 48 89 d7 e8 5c e7 a5 ff e9 4a
RSP: 0018:ffffc9000a1af690 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000ffffe428 RCX: ffffffff823665c1
RDX: ffff88802b52a1c0 RSI: ffffffff823665cf RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000005 R12: ffff88806442ac08
R13: 0000000000000002 R14: 1ffff92001435ee1 R15: ffff88806440c868
FS: 00007fbecfbfe6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020027040 CR3: 000000007c40e000 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.
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:[~2023-11-25 10:34 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=0000000000009800de060af79c8f@google.com \
--to=syzbot+64f520f6fe02b8947407@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.