| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <BBB1284B-A829-417D-8DD7-83371147F876@nvidia.com> Date: Sat, 30 Aug 2025 21:45:05 -0400 From: Zi Yan <ziy@...dia.com> To: syzbot <syzbot+2f3c8569e4b7486452ae@...kaller.appspotmail.com> Cc: akpm@...ux-foundation.org, apopple@...dia.com, byungchul@...com, david@...hat.com, gourry@...rry.net, joshua.hahnjy@...il.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org, matthew.brost@...el.com, rakie.kim@...com, syzkaller-bugs@...glegroups.com, ying.huang@...ux.alibaba.com Subject: Re: [syzbot] [mm?] WARNING in new_slab (2) #syz dup: [syzbot] [mm?] WARNING in xfs_init_fs_context Link: https://lore.kernel.org/all/6861c281.a70a0220.3b7e22.0ab8.GAE@google.com/T/ On 30 Aug 2025, at 21:38, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: fab1beda7597 Merge tag 'devicetree-fixes-for-6.17-1' of gi.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=16ad77bc580000 > kernel config: https://syzkaller.appspot.com/x/.config?x=fecbb496f75d3d61 > dashboard link: https://syzkaller.appspot.com/bug?extid=2f3c8569e4b7486452ae > compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 > userspace arch: i386 > > Unfortunately, I don't have any reproducer for this issue yet. > > Downloadable assets: > disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-fab1beda.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/813fdba24db0/vmlinux-fab1beda.xz > kernel image: https://storage.googleapis.com/syzbot-assets/12a740d2c9a6/bzImage-fab1beda.xz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+2f3c8569e4b7486452ae@...kaller.appspotmail.com > > ------------[ cut here ]------------ > WARNING: CPU: 1 PID: 10417 at mm/page_alloc.c:4619 __alloc_pages_slowpath mm/page_alloc.c:4619 [inline] > WARNING: CPU: 1 PID: 10417 at mm/page_alloc.c:4619 __alloc_frozen_pages_noprof+0x1f21/0x23f0 mm/page_alloc.c:5161 > Modules linked in: > CPU: 1 UID: 0 PID: 10417 Comm: syz.1.1147 Not tainted syzkaller #0 PREEMPT(full) > Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 > RIP: 0010:__alloc_pages_slowpath mm/page_alloc.c:4619 [inline] > RIP: 0010:__alloc_frozen_pages_noprof+0x1f21/0x23f0 mm/page_alloc.c:5161 > Code: 90 0f 0b 90 e9 0d f9 ff ff e8 bb d6 0c 00 e9 43 f1 ff ff 4c 89 ff e8 ae d6 0c 00 e9 1e f1 ff ff 90 0f 0b 90 e9 3b fb ff ff 90 <0f> 0b 90 e9 24 fb ff ff 89 b4 24 90 00 00 00 48 89 54 24 50 e8 56 > RSP: 0018:ffffc90003a477f8 EFLAGS: 00010202 > RAX: 0000000000008000 RBX: 0000000000000000 RCX: ffffc90003a4792c > RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88803fffd9b8 > RBP: 0000000000048cc0 R08: 0000000000004f8b R09: 00000000000043f1 > R10: 0000000000000000 R11: ffffc90003a47920 R12: ffff88803fffbb80 > R13: 1ffff92000748f14 R14: 0000000000000000 R15: 0000000000000002 > FS: 0000000000000000(0000) GS:ffff8880975c3000(0063) knlGS:00000000f5484b40 > CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 > CR2: 00000000326f2ffc CR3: 0000000070630000 CR4: 0000000000352ef0 > Call Trace: > <TASK> > alloc_pages_mpol+0x1fb/0x550 mm/mempolicy.c:2416 > alloc_slab_page mm/slub.c:2487 [inline] > allocate_slab mm/slub.c:2663 [inline] > new_slab+0x265/0x330 mm/slub.c:2709 > ___slab_alloc+0xcf2/0x1740 mm/slub.c:3891 > __slab_alloc.constprop.0+0x56/0xb0 mm/slub.c:3981 > __slab_alloc_node mm/slub.c:4056 [inline] > slab_alloc_node mm/slub.c:4217 [inline] > __kmalloc_cache_noprof+0xfb/0x3e0 mm/slub.c:4391 > kmalloc_noprof include/linux/slab.h:905 [inline] > kzalloc_noprof include/linux/slab.h:1039 [inline] > xfs_init_fs_context+0x45/0x5e0 fs/xfs/xfs_super.c:2278 > alloc_fs_context+0x54d/0x9c0 fs/fs_context.c:318 > do_new_mount fs/namespace.c:3787 [inline] > path_mount+0xbdd/0x2000 fs/namespace.c:4123 > do_mount fs/namespace.c:4136 [inline] > __do_sys_mount fs/namespace.c:4347 [inline] > __se_sys_mount fs/namespace.c:4324 [inline] > __ia32_sys_mount+0x28b/0x310 fs/namespace.c:4324 > do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline] > __do_fast_syscall_32+0x7c/0x3a0 arch/x86/entry/syscall_32.c:306 > do_fast_syscall_32+0x32/0x80 arch/x86/entry/syscall_32.c:331 > entry_SYSENTER_compat_after_hwframe+0x84/0x8e > RIP: 0023:0xf7fa4579 > Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 > RSP: 002b:00000000f548455c EFLAGS: 00000296 ORIG_RAX: 0000000000000015 > RAX: ffffffffffffffda RBX: 0000000080000140 RCX: 0000000080000040 > RDX: 0000000080000080 RSI: 0000000002208004 RDI: 0000000000000000 > RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 > R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000 > R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 > </TASK> > ---------------- > Code disassembly (best guess), 2 bytes skipped: > 0: 10 06 adc %al,(%rsi) > 2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi > 6: 10 07 adc %al,(%rdi) > 8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi > c: 10 08 adc %cl,(%rax) > e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi > 1e: 00 51 52 add %dl,0x52(%rcx) > 21: 55 push %rbp > 22: 89 e5 mov %esp,%ebp > 24: 0f 34 sysenter > 26: cd 80 int $0x80 > * 28: 5d pop %rbp <-- trapping instruction > 29: 5a pop %rdx > 2a: 59 pop %rcx > 2b: c3 ret > 2c: 90 nop > 2d: 90 nop > 2e: 90 nop > 2f: 90 nop > 30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi > 37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi > > > --- > 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@...glegroups.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 -- Best Regards, Yan, Zi
Powered by blists - more mailing lists