From: syzbot <syzbot+9316d51d9d379787e4ad@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: [syzbot] [ext4?] WARNING in ext4_mb_add_groupinfo
Date: Sun, 09 Jun 2024 05:28:28 -0700 [thread overview]
Message-ID: <0000000000007e1964061a742b0a@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 32f88d65f01b Merge tag 'linux_kselftest-fixes-6.10-rc3' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105806bc980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a1d4156cdd1d8e2
dashboard link: https://syzkaller.appspot.com/bug?extid=9316d51d9d379787e4ad
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-32f88d65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4330b2cd167b/vmlinux-32f88d65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/961415fd7b0b/bzImage-32f88d65.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9316d51d9d379787e4ad@syzkaller.appspotmail.com
loop3: detected capacity change from 0 to 1024
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(l->owner)
WARNING: CPU: 3 PID: 7049 at include/linux/local_lock_internal.h:30 local_lock_acquire include/linux/local_lock_internal.h:30 [inline]
WARNING: CPU: 3 PID: 7049 at include/linux/local_lock_internal.h:30 ___slab_alloc+0x16c2/0x1870 mm/slub.c:3715
Modules linked in:
CPU: 3 PID: 7049 Comm: syz-executor.3 Not tainted 6.10.0-rc2-syzkaller-00022-g32f88d65f01b #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:local_lock_acquire include/linux/local_lock_internal.h:30 [inline]
RIP: 0010:___slab_alloc+0x16c2/0x1870 mm/slub.c:3715
Code: a0 02 85 c0 74 09 83 3d 0f f3 04 0e 00 74 21 90 e9 30 ff ff ff 90 48 c7 c6 ff 20 3b 8d 48 c7 c7 28 ec 3a 8d e8 0f 5a 70 ff 90 <0f> 0b 90 90 eb c6 90 48 c7 c6 08 21 3b 8d 48 c7 c7 28 ec 3a 8d e8
RSP: 0018:ffffc9000394f830 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffffc90003db1000
RDX: 0000000000040000 RSI: ffffffff81500016 RDI: 0000000000000001
RBP: ffffc9000394f910 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 000000002d2d2d2d R12: ffff888024f90000
R13: ffff88804aaa4dc0 R14: ffffe8fefd34e860 R15: ffffe8fefd34e840
FS: 00007fe0ca3416c0(0000) GS:ffff88806b300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c42d000 CR3: 000000001ebea000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__slab_alloc.constprop.0+0x56/0xb0 mm/slub.c:3756
__slab_alloc_node mm/slub.c:3809 [inline]
slab_alloc_node mm/slub.c:3988 [inline]
kmem_cache_alloc_noprof+0x2a7/0x2f0 mm/slub.c:4007
ext4_mb_add_groupinfo+0x445/0x1180 fs/ext4/mballoc.c:3355
ext4_mb_init_backend fs/ext4/mballoc.c:3434 [inline]
ext4_mb_init+0x127a/0x2530 fs/ext4/mballoc.c:3732
__ext4_fill_super fs/ext4/super.c:5501 [inline]
ext4_fill_super+0x6d4f/0xace0 fs/ext4/super.c:5676
get_tree_bdev+0x36f/0x610 fs/super.c:1615
vfs_get_tree+0x8f/0x380 fs/super.c:1780
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe0c967e5ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007fe0ca340ef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fe0ca340f80 RCX: 00007fe0c967e5ea
RDX: 0000000020000040 RSI: 0000000020000200 RDI: 00007fe0ca340f40
RBP: 0000000020000040 R08: 00007fe0ca340f80 R09: 0000000000200000
R10: 0000000000200000 R11: 0000000000000202 R12: 0000000020000200
R13: 00007fe0ca340f40 R14: 000000000000057c R15: 0000000020000180
</TASK>
---
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 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-06-09 12:28 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=0000000000007e1964061a742b0a@google.com \
--to=syzbot+9316d51d9d379787e4ad@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@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.