[v5.15] WARNING in ovl_workdir_create

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=137a613e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=875d98826c53bf16
dashboard link: https://syzkaller.appspot.com/bug?extid=09497d2fbca70ab5a5d9
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/f227a150ea92/disk-4878aadf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6cfc50bf8b4e/vmlinux-4878aadf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23f7adc3c761/bzImage-4878aadf.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff8880652936d0, owner = 0x0, curr 0xffff888021623b80, list empty
WARNING: CPU: 0 PID: 5167 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 0 PID: 5167 at kernel/locking/rwsem.c:1350 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 5167 Comm: syz.2.447 Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1604
Code: 48 c7 c7 80 1d 8b 8a 48 c7 c6 40 20 8b 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 cf 0e ea ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 c8 9f e4 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90002fa7680 EFLAGS: 00010292
RAX: 7d4afc6a071e3400 RBX: ffffffff8a8b1e60 RCX: 0000000000040000
RDX: ffffc9000b399000 RSI: 0000000000023ed2 RDI: 0000000000023ed3
RBP: ffffc90002fa7750 R08: ffffffff8166835c R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff8880652936d0 R14: 1ffff920005f4ed8 R15: dffffc0000000000
FS: 00007fbba5c2e6c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002001a000 CR3: 0000000062dfa000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:794 [inline]
ovl_workdir_create+0x73f/0x7d0 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1374 [inline]
ovl_get_workdir+0x3ab/0x1350 fs/overlayfs/super.c:1524
ovl_fill_super+0x1b85/0x2a20 fs/overlayfs/super.c:2080
mount_nodev+0x52/0xe0 fs/super.c:1433
legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1517
do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fbba71ced39
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:00007fbba5c2e048 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fbba735d070 RCX: 00007fbba71ced39
RDX: 0000000020000080 RSI: 00000000200022c0 RDI: 0000000000000000
RBP: 00007fbba724f766 R08: 0000000020000900 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fbba735d070 R15: 00007ffc8d08db58
</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