All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+78a7af91b68fc6394771@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jannh@google.com, liam@infradead.org,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	ljs@kernel.org,  pfalcato@suse.de,
	syzkaller-bugs@googlegroups.com, vbabka@kernel.org
Subject: [syzbot] [mm?] WARNING in mas_nomem
Date: Fri, 31 Jul 2026 00:30:32 -0700	[thread overview]
Message-ID: <6a6c4f18.b1a781d0.210f9.001f.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    cc2b5f627e8c Add linux-next specific files for 20260714
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15ce5632580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2290ccbf984c524f
dashboard link: https://syzkaller.appspot.com/bug?extid=78a7af91b68fc6394771
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=179151b9580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6836f8efb1da/disk-cc2b5f62.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0109d3477cc7/vmlinux-cc2b5f62.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c2e49e350bbf/bzImage-cc2b5f62.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+78a7af91b68fc6394771@syzkaller.appspotmail.com

------------[ cut here ]------------
!mas->sheaf && !mas->alloc
WARNING: lib/maple_tree.c:5751 at mas_nomem+0x1cc/0x210 lib/maple_tree.c:5751, CPU#0: udevd/5627
Modules linked in:
CPU: 0 UID: 0 PID: 5627 Comm: udevd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:mas_nomem+0x1cc/0x210 lib/maple_tree.c:5751
Code: 4c 89 ff e8 d6 85 ea f6 49 c7 07 00 00 00 00 b0 01 e9 95 fe ff ff e8 f3 2d 7e f6 90 0f 0b 90 e9 2b ff ff ff e8 e5 2d 7e f6 90 <0f> 0b 90 e9 77 fe ff ff 89 d1 80 e1 07 80 c1 03 38 c1 0f 8c ce fe
RSP: 0018:ffffc9000562f8f0 EFLAGS: 00010293
RAX: ffffffff8b4775cb RBX: 1ffff92000ac5fbf RCX: ffff8880366e3e80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000cc0 R08: 00000000ffffffff R09: 1ffffffff1ca1a86
R10: dffffc0000000000 R11: fffffbfff1ca1a87 R12: dffffc0000000000
R13: ffffc9000562fe18 R14: ffffc9000562fde0 R15: ffffc9000562fdf8
FS:  00007f9021203880(0000) GS:ffff8881259f2000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056467bb0d750 CR3: 0000000046416000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 mas_store_gfp+0x37a/0x820 lib/maple_tree.c:4987
 vma_iter_clear_gfp include/linux/mm.h:1674 [inline]
 do_vmi_align_munmap+0x30c/0x4d0 mm/vma.c:1644
 do_vmi_munmap+0x252/0x2d0 mm/vma.c:1697
 __vm_munmap+0x241/0x3e0 mm/vma.c:3347
 __do_sys_munmap mm/mmap.c:1079 [inline]
 __se_sys_munmap mm/mmap.c:1076 [inline]
 __x64_sys_munmap+0x60/0x70 mm/mmap.c:1076
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x17b/0x530 arch/x86/entry/syscall_64.c:85
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9021368097
Code: 73 01 c3 48 8b 0d 61 2d 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 31 2d 0d 00 f7 d8 64 89 01 48
RSP: 002b:00007ffeaf32d0a8 EFLAGS: 00000206 ORIG_RAX: 000000000000000b
RAX: ffffffffffffffda RBX: 000056467bad9bf0 RCX: 00007f9021368097
RDX: 0000000000000000 RSI: 00000000009480e8 RDI: 00007f90208ba000
RBP: 000056467bad9910 R08: 000056467baec140 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000206 R12: 00005646569e2588
R13: 00007ffeaf32d130 R14: 0000000000000000 R15: 0000000000000000
 </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 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:[~2026-07-31  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  7:30 syzbot [this message]
2026-07-31 15:59 ` [syzbot] [mm?] WARNING in mas_nomem Liam R. Howlett
2026-07-31 16:07   ` Vlastimil Babka (SUSE)
2026-08-05  0:46     ` Jason Gunthorpe
2026-08-05  8:01       ` Vlastimil Babka (SUSE)
2026-08-06 14:29         ` Liam R. Howlett
2026-08-06 15:48           ` Jason Gunthorpe
2026-08-07 13:19             ` Liam R. Howlett
2026-08-07 19:24               ` Liam R. Howlett
2026-08-07 19:26                 ` Jason Gunthorpe
2026-08-07 20:32                   ` Liam R. Howlett

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=6a6c4f18.b1a781d0.210f9.001f.GAE@google.com \
    --to=syzbot+78a7af91b68fc6394771@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=pfalcato@suse.de \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@kernel.org \
    /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.