BUG: spinlock bad magic in unmap_page_range
6 views
Skip to first unread message
syzbot
May 11, 2021, 7:10:17 PM5/11/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147e2ce9d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=eee676968875ee4afcce
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eee676...@syzkaller.appspotmail.com
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
BUG: spinlock bad magic on CPU#1, systemd-udevd/8412
lock: 0xffff88800010f898, .magic: 00000000, .owner: <none>/-1, .owner_cpu: -1
CPU: 1 PID: 8412 Comm: systemd-udevd Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
do_raw_spin_lock+0x18e/0x200 kernel/locking/spinlock_debug.c:112
spin_lock include/linux/spinlock.h:317 [inline]
zap_pte_range mm/memory.c:1315 [inline]
zap_pmd_range mm/memory.c:1456 [inline]
zap_pud_range mm/memory.c:1485 [inline]
zap_p4d_range mm/memory.c:1506 [inline]
unmap_page_range+0x887/0x1ce0 mm/memory.c:1527
unmap_single_vma+0x147/0x2b0 mm/memory.c:1572
unmap_vmas+0x9d/0x160 mm/memory.c:1602
exit_mmap+0x270/0x4d0 mm/mmap.c:3058
__mmput kernel/fork.c:930 [inline]
mmput kernel/fork.c:951 [inline]
mmput+0xfa/0x420 kernel/fork.c:946
exit_mm kernel/exit.c:548 [inline]
do_exit+0x984/0x2850 kernel/exit.c:855
do_group_exit+0x100/0x2e0 kernel/exit.c:965
SYSC_exit_group kernel/exit.c:976 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:974
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f82ad4f8618
RSP: 002b:00007ffd9003ef48 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007ffd9003f010 RCX: 00007f82ad4f8618
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00007ffd9003f0c0 R08: 00000000000000e7 R09: fffffffffffffe50
R10: 00000000ffffffff R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on loop5
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
EXT4-fs warning (device sda1): verify_group_input:131: Cannot add at group 9 (only 16 groups)
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 84 bytes leftover after parsing attributes in process `syz-executor.5'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
FAT-fs (loop5): Unrecognized mount option "context=staff_u" or missing value
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
NFS: bad mount option value specified: v7
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
qnx4: no qnx4 filesystem (no root dir).
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
qnx4: no qnx4 filesystem (no root dir).
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
---
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.
syzbot found the following issue on:
HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147e2ce9d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=eee676968875ee4afcce
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eee676...@syzkaller.appspotmail.com
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
BUG: spinlock bad magic on CPU#1, systemd-udevd/8412
lock: 0xffff88800010f898, .magic: 00000000, .owner: <none>/-1, .owner_cpu: -1
CPU: 1 PID: 8412 Comm: systemd-udevd Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
do_raw_spin_lock+0x18e/0x200 kernel/locking/spinlock_debug.c:112
spin_lock include/linux/spinlock.h:317 [inline]
zap_pte_range mm/memory.c:1315 [inline]
zap_pmd_range mm/memory.c:1456 [inline]
zap_pud_range mm/memory.c:1485 [inline]
zap_p4d_range mm/memory.c:1506 [inline]
unmap_page_range+0x887/0x1ce0 mm/memory.c:1527
unmap_single_vma+0x147/0x2b0 mm/memory.c:1572
unmap_vmas+0x9d/0x160 mm/memory.c:1602
exit_mmap+0x270/0x4d0 mm/mmap.c:3058
__mmput kernel/fork.c:930 [inline]
mmput kernel/fork.c:951 [inline]
mmput+0xfa/0x420 kernel/fork.c:946
exit_mm kernel/exit.c:548 [inline]
do_exit+0x984/0x2850 kernel/exit.c:855
do_group_exit+0x100/0x2e0 kernel/exit.c:965
SYSC_exit_group kernel/exit.c:976 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:974
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f82ad4f8618
RSP: 002b:00007ffd9003ef48 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007ffd9003f010 RCX: 00007f82ad4f8618
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00007ffd9003f0c0 R08: 00000000000000e7 R09: fffffffffffffe50
R10: 00000000ffffffff R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on loop5
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
EXT4-fs warning (device sda1): verify_group_input:131: Cannot add at group 9 (only 16 groups)
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 72 bytes leftover after parsing attributes in process `syz-executor.4'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 84 bytes leftover after parsing attributes in process `syz-executor.5'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
FAT-fs (loop5): Unrecognized mount option "context=staff_u" or missing value
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
NFS: bad mount option value specified: v7
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
qnx4: no qnx4 filesystem (no root dir).
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
qnx4: no qnx4 filesystem (no root dir).
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
VFS: unable to read V7 FS superblock on device loop4.
VFS: could not find a valid V7 on loop4.
---
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.
syzbot
Sep 8, 2021, 7:10:19 PM9/8/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages