[syzbot] [mtd?] WARNING in add_mtd_device

* [syzbot] [mtd?] WARNING in add_mtd_device
@ 2026-06-20  8:22 ` syzbot
  0 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2026-06-20  8:22 UTC (permalink / raw)
  To: linux-kernel, linux-mtd, miquel.raynal, richard, syzkaller-bugs,
	vigneshr

Hello,

syzbot found the following issue on:

HEAD commit:    a975094bf98c Merge tag 'exfat-for-7.2-rc1' of git://git.ke..
git tree:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux master
console output: https://syzkaller.appspot.com/x/log.txt?x=16e3dd56580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3c66dc15e483c558
dashboard link: https://syzkaller.appspot.com/bug?extid=3ae80219c633aca5431c
compiler:       aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/fa3fbcfdac58/non_bootable_disk-a975094b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/56fd6dc1b679/vmlinux-a975094b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b1422518a402/Image-a975094b.gz.xz

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

mtd partition "" doesn't have enough space: 0x8000003 < 0x8000084bb, disabled
------------[ cut here ]------------
WARNING: drivers/mtd/mtdcore.c:719 at add_mtd_device+0x56c/0x14cc drivers/mtd/mtdcore.c:719, CPU#1: syz.0.5209/17410
Modules linked in:
CPU: 1 UID: 0 PID: 17410 Comm: syz.0.5209 Tainted: G             L      syzkaller #0 PREEMPT 
Tainted: [L]=SOFTLOCKUP
Hardware name: linux,dummy-virt (DT)
pstate: 10000005 (nzcV daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : add_mtd_device+0x56c/0x14cc drivers/mtd/mtdcore.c:719
lr : mtd_add_partition+0x218/0x48c drivers/mtd/mtdpart.c:280
sp : ffff80008e3b76f0
x29: ffff80008e3b77b0 x28: ffff000015758000 x27: ffff00001783c004
x26: 1fffe00002f0783f x25: ffff00001783c014 x24: 0000000000000004
x23: ffff00001783c000 x22: 1ffff00011c76f02 x21: 0000000000000000
x20: ffff00001783c1a0 x19: 0000000000000c00 x18: 0000000000000000
x17: 3830303030387830 x16: 203c203330303030 x15: 30387830203a6563
x14: 617073206867756f x13: 0000000000000001 x12: ffff700011c76ee9
x11: 1ffff00011c76ee8 x10: ffff700011c76ee8 x9 : dfff800000000000
x8 : ffff80008e3b7747 x7 : 1ffff00011c76eea x6 : 0000000041b58ab3
x5 : ffff700011c76eea x4 : ffff80008e3b7750 x3 : 1fffe00002f07800
x2 : 0000000000000000 x1 : 0000000000000007 x0 : 0000000000000000
Call trace:
 add_mtd_device+0x56c/0x14cc drivers/mtd/mtdcore.c:719 (P)
 mtd_add_partition+0x218/0x48c drivers/mtd/mtdpart.c:280
 mtdchar_blkpg_ioctl+0x17c/0x1b8 drivers/mtd/mtdchar.c:562
 mtdchar_ioctl+0x2f8/0x1ed8 drivers/mtd/mtdchar.c:1218
 mtdchar_unlocked_ioctl+0xa0/0xfc drivers/mtd/mtdchar.c:1241
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __arm64_sys_ioctl+0x124/0x1a4 fs/ioctl.c:583
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x74/0x240 arch/arm64/kernel/syscall.c:49
 el0_svc_common.constprop.0+0xac/0x230 arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x40/0x58 arch/arm64/kernel/syscall.c:140
 el0_svc+0x58/0x2a4 arch/arm64/kernel/entry-common.c:736
 el0t_64_sync_handler+0xa0/0xe4 arch/arm64/kernel/entry-common.c:755
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594
irq event stamp: 0
hardirqs last  enabled at (0): [<0000000000000000>] 0x0
hardirqs last disabled at (0): [<ffff800080215cc8>] copy_process+0x16a8/0x5700 kernel/fork.c:2232
softirqs last  enabled at (0): [<ffff800080215ce8>] copy_process+0x16c8/0x5700 kernel/fork.c:2233
softirqs last disabled at (0): [<0000000000000000>] 0x0
---[ end trace 0000000000000000 ]---

---
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

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

^ permalink raw reply	[flat|nested] 6+ messages in thread