Hello,
syzbot found the following issue on:
HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=14268bb0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=1eebf09bc04ebd78
dashboard link:
https://syzkaller.appspot.com/bug?extid=dfd64589ce751f962e0b
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/bccba205a29a/disk-344a0965.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/bdca79b3b5db/vmlinux-344a0965.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/6c2271a91ef3/bzImage-344a0965.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+dfd645...@syzkaller.appspotmail.com
gfs2: fsid=syz:syz.0: first mount done, others may mount
------------[ cut here ]------------
WARNING: CPU: 0 PID: 15338 at mm/page_alloc.c:5582 __alloc_pages+0x3b7/0x770 mm/page_alloc.c:5582
Modules linked in:
CPU: 0 PID: 15338 Comm: syz.3.3109 Not tainted 6.1.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:__alloc_pages+0x3b7/0x770 mm/page_alloc.c:5582
Code: fc ff df 0f 85 fa 00 00 00 44 89 e9 81 e1 7f ff ff ff a9 00 00 04 00 41 0f 44 cd 41 89 cd e9 ea 00 00 00 c6 05 e6 37 b6 0c 01 <0f> 0b 41 83 fc 0a 0f 86 1e fd ff ff 45 31 e4 48 c7 44 24 20 0e 36
RSP: 0018:ffffc900038074e0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90003807568
RBP: ffffc900038075f8 R08: dffffc0000000000 R09: ffffc90003807540
R10: 0000000000000000 R11: dffffc0000000001 R12: 000000000000000c
R13: 0000000000040d40 R14: 1ffff92000700ea4 R15: 1ffff92000700ea0
FS: 00007fad0d72d6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c404f30 CR3: 0000000073a84000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]
__kmalloc_large_node+0x91/0x1d0 mm/slab_common.c:1077
__do_kmalloc_node mm/slab_common.c:924 [inline]
__kmalloc+0x118/0x230 mm/slab_common.c:949
kmalloc_array include/linux/slab.h:615 [inline]
kcalloc include/linux/slab.h:646 [inline]
compute_bitstructs fs/gfs2/rgrp.c:766 [inline]
read_rindex_entry fs/gfs2/rgrp.c:931 [inline]
gfs2_ri_update+0x532/0x18d0 fs/gfs2/rgrp.c:1001
gfs2_rindex_update+0x32f/0x3f0 fs/gfs2/rgrp.c:1051
init_inodes+0x249/0x310 fs/gfs2/ops_fstype.c:917
gfs2_fill_super+0x1c40/0x2770 fs/gfs2/ops_fstype.c:1246
get_tree_bdev+0x3fe/0x620 fs/super.c:1366
gfs2_get_tree+0x50/0x210 fs/gfs2/ops_fstype.c:1327
vfs_get_tree+0x88/0x270 fs/super.c:1573
do_new_mount+0x2ba/0xb40 fs/namespace.c:3056
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3584
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fad0c98e90a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fad0d72ce68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fad0d72cef0 RCX: 00007fad0c98e90a
RDX: 0000200000000240 RSI: 0000200000001c00 RDI: 00007fad0d72ceb0
RBP: 0000200000000240 R08: 00007fad0d72cef0 R09: 0000000000000804
R10: 0000000000000804 R11: 0000000000000246 R12: 0000200000001c00
R13: 00007fad0d72ceb0 R14: 000000000001260b R15: 0000200000000280
</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
syzk...@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