[v6.1] WARNING in unlock_mount (3)
8 views
Skip to first unread message
syzbot
Nov 24, 2024, 4:42:21 AM11/24/24
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1089d75f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2033991697223b4d
dashboard link: https://syzkaller.appspot.com/bug?extid=40c6d9d0f3a9047be761
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ade76a251c5e/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75b37498c5b7/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4eaeba71c1b6/Image-e4d90d63.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+40c6d9...@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000f4992930, owner = 0x0, curr 0xffff0000c4141bc0, list empty
WARNING: CPU: 1 PID: 5541 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 5541 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 5541 Comm: syz.5.244 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1371 [inline]
pc : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
sp : ffff8000219479e0
x29: ffff800021947a70 x28: 1ffff00004328f68 x27: 1fffe0001e932533
x26: dfff800000000000 x25: 1fffe0001e932527 x24: ffff0000f4992988
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000c4141bc0
x20: ffff0000f4992930 x19: ffff0000f4992930 x18: ffff800021947580
x17: 0000000000000000 x16: ffff8000122975f4 x15: 0000000000000002
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000080000
x11: 0000000000014d05 x10: ffff8000331ba000 x9 : 98ca58230759aa00
x8 : 98ca58230759aa00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff8000219472d8 x4 : ffff800015ab30e0 x3 : ffff800008585a08
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:763 [inline]
unlock_mount+0x1d8/0x244 fs/namespace.c:2325
do_new_mount_fc fs/namespace.c:2999 [inline]
do_new_mount+0x700/0x8fc fs/namespace.c:3058
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3584
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 294
hardirqs last enabled at (293): [<ffff80000833eab0>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (294): [<ffff8000122932ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (256): [<ffff8000081c1c58>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (256): [<ffff8000081c1c58>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (237): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605
---[ 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 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
syzbot found the following issue on:
HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1089d75f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2033991697223b4d
dashboard link: https://syzkaller.appspot.com/bug?extid=40c6d9d0f3a9047be761
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ade76a251c5e/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75b37498c5b7/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4eaeba71c1b6/Image-e4d90d63.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+40c6d9...@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000f4992930, owner = 0x0, curr 0xffff0000c4141bc0, list empty
WARNING: CPU: 1 PID: 5541 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 5541 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 5541 Comm: syz.5.244 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1371 [inline]
pc : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
sp : ffff8000219479e0
x29: ffff800021947a70 x28: 1ffff00004328f68 x27: 1fffe0001e932533
x26: dfff800000000000 x25: 1fffe0001e932527 x24: ffff0000f4992988
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000c4141bc0
x20: ffff0000f4992930 x19: ffff0000f4992930 x18: ffff800021947580
x17: 0000000000000000 x16: ffff8000122975f4 x15: 0000000000000002
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000080000
x11: 0000000000014d05 x10: ffff8000331ba000 x9 : 98ca58230759aa00
x8 : 98ca58230759aa00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff8000219472d8 x4 : ffff800015ab30e0 x3 : ffff800008585a08
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:763 [inline]
unlock_mount+0x1d8/0x244 fs/namespace.c:2325
do_new_mount_fc fs/namespace.c:2999 [inline]
do_new_mount+0x700/0x8fc fs/namespace.c:3058
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3584
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 294
hardirqs last enabled at (293): [<ffff80000833eab0>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (294): [<ffff8000122932ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (256): [<ffff8000081c1c58>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (256): [<ffff8000081c1c58>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (237): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605
---[ 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 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
syzbot
Mar 31, 2025, 10:44:16 AM3/31/25
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.
syzbot
Apr 1, 2025, 10:56:19 PM4/1/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 0c935c049b5c Linux 5.15.179
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117f094c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=98c228fbc016eb3a
dashboard link: https://syzkaller.appspot.com/bug?extid=e62fb674504ae5f0b786
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d5477072f336/disk-0c935c04.raw.xz
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/77d15907ffb3/vmlinux-0c935c04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/efe5d79cb16a/Image-0c935c04.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000f08a9950, owner = 0x0, curr 0xffff0000c73ab680, list empty
WARNING: CPU: 1 PID: 7844 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 7844 at kernel/locking/rwsem.c:1350 up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 7844 Comm: syz.5.579 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1349 [inline]
pc : up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
lr : __up_write kernel/locking/rwsem.c:1349 [inline]
lr : up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
sp : ffff800020aa7a30
x29: ffff800020aa7a40 x28: 1ffff00004154f60 x27: 1fffe0001d13cc2f
x26: dfff800000000000 x25: 1fffe0001e115337 x24: ffff0000f08a99a8
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000c73ab680
x20: ffff0000f08a9950 x19: ffff0000f08a9950 x18: 1fffe0003683298e
x17: 1fffe0003683298e x16: ffff800011b5ac80 x15: ffff800014c0f2a0
x14: 1ffff0000296e06c x13: dfff800000000000 x12: 0000000000080000
x11: 0000000000011581 x10: ffff80002cc07000 x9 : a8b273ff8da4e200
x8 : a8b273ff8da4e200 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000aa1313c
x2 : ffff0001b4194d10 x1 : 0000000100000000 x0 : 00000000000000bd
Call trace:
__up_write kernel/locking/rwsem.c:1349 [inline]
up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
inode_unlock include/linux/fs.h:792 [inline]
unlock_mount+0x1d8/0x244 fs/namespace.c:2281
do_new_mount_fc fs/namespace.c:2955 [inline]
do_new_mount+0x700/0x8fc fs/namespace.c:3014
path_mount+0x594/0x101c fs/namespace.c:3342
do_mount fs/namespace.c:3355 [inline]
__do_sys_mount fs/namespace.c:3563 [inline]
__se_sys_mount fs/namespace.c:3540 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3540
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 506
hardirqs last enabled at (505): [<ffff80000826b288>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (505): [<ffff80000826b288>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:4783
hardirqs last disabled at (506): [<ffff800011b56334>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (500): [<ffff8000081b70b8>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (500): [<ffff8000081b70b8>] handle_softirqs+0xb88/0xdbc kernel/softirq.c:586
softirqs last disabled at (317): [<ffff8000081b7750>] __do_softirq kernel/softirq.c:592 [inline]
softirqs last disabled at (317): [<ffff8000081b7750>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (317): [<ffff8000081b7750>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (317): [<ffff8000081b7750>] __irq_exit_rcu+0x268/0x4d8 kernel/softirq.c:641
---[ end trace c42e49c2dce2b5ce ]---
syzbot
Jul 10, 2025, 10:56:14 PM7/10/25
to syzkaller...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages