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=12201fc0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link:
https://syzkaller.appspot.com/bug?extid=a294453cfd42b71c2608
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/19f991f20183/disk-e4d90d63.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/61eb5f055f38/vmlinux-e4d90d63.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/0ddd97416681/bzImage-e4d90d63.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a29445...@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888050ed7930, owner = 0x0, curr 0xffff88802a95d940, list empty
WARNING: CPU: 1 PID: 10793 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 10793 at kernel/locking/rwsem.c:1372 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 10793 Comm: syz.1.1539 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1371 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Code: 48 c7 c7 60 f5 0b 8b 48 c7 c6 a0 f7 0b 8b 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 5f c3 e8 ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 78 2c 9b 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90003707640 EFLAGS: 00010292
RAX: c3d89351fa914500 RBX: ffffffff8b0bf640 RCX: 0000000000080000
RDX: ffffc90005c6a000 RSI: 000000000002be64 RDI: 000000000002be65
RBP: ffffc90003707710 R08: ffffffff8152b88e R09: fffff520006e0e29
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888050ed7930 R14: 1ffff920006e0ed0 R15: dffffc0000000000
FS: 00007f538a33e6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faebef1cc91 CR3: 000000007e0ab000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:763 [inline]
ovl_workdir_create+0x8ea/0x9d0 fs/overlayfs/super.c:842
ovl_make_workdir fs/overlayfs/super.c:1389 [inline]
ovl_get_workdir+0x3b7/0x17b0 fs/overlayfs/super.c:1539
ovl_fill_super+0x1b85/0x2a20 fs/overlayfs/super.c:2095
mount_nodev+0x52/0xe0 fs/super.c:1489
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1573
do_new_mount+0x2ba/0xb40 fs/namespace.c:3056
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3584
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f538957ff19
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f538a33e058 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f5389746080 RCX: 00007f538957ff19
RDX: 0000000020000080 RSI: 00000000200000c0 RDI: 0000000000000000
RBP: 00007f53895f3986 R08: 0000000020000180 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f5389746080 R15: 00007ffc6b4f2ca8
</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
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