[v5.15] WARNING in ovl_workdir_create (4)
0 views
Skip to first unread message
syzbot
Apr 4, 2026, 3:44:31 PM (yesterday) Apr 4
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151388f2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=51216c95e1873f4c4098
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51216c...@syzkaller.appspotmail.com
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x1, magic = 0xffff888058063e30, owner = 0xffff888028d03b80, curr 0xffff888022398000, list empty
WARNING: CPU: 1 PID: 4851 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 4851 at kernel/locking/rwsem.c:1350 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 0 PID: 4851 Comm: syz.3.102 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Code: 44 d0 48 c7 c7 00 1b 2b 8a 48 c7 c6 c0 1d 2b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 53 1f 55 08 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 08 17 8a 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000317f790 EFLAGS: 00010296
RAX: 587a7f9489240e00 RBX: ffff888058063e30 RCX: 0000000000080000
RDX: ffffc9000f1fd000 RSI: 0000000000030d0f RDI: 0000000000030d10
RBP: dffffc0000000000 R08: ffff8880b9133d7f R09: 1ffff110172267af
R10: dffffc0000000000 R11: ffffed10172267b0 R12: ffff888028d03b80
R13: ffff888058063e88 R14: ffff888058063e30 R15: 1ffff1100b00c7c7
FS: 00007f8d82f246c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c2b54d0 CR3: 000000001f9c9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
ovl_workdir_create+0x57f/0x630 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1376 [inline]
ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526
ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082
mount_nodev+0x52/0xe0 fs/super.c:1446
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8d84ceb819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8d82f24028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f8d84f65090 RCX: 00007f8d84ceb819
RDX: 0000200000000440 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f8d84d81c91 R08: 0000200000000080 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8d84f65128 R14: 00007f8d84f65090 R15: 00007ffc01e8bbc8
</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
syzbot found the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151388f2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=51216c95e1873f4c4098
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51216c...@syzkaller.appspotmail.com
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x1, magic = 0xffff888058063e30, owner = 0xffff888028d03b80, curr 0xffff888022398000, list empty
WARNING: CPU: 1 PID: 4851 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 4851 at kernel/locking/rwsem.c:1350 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 0 PID: 4851 Comm: syz.3.102 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Code: 44 d0 48 c7 c7 00 1b 2b 8a 48 c7 c6 c0 1d 2b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 53 1f 55 08 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 08 17 8a 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000317f790 EFLAGS: 00010296
RAX: 587a7f9489240e00 RBX: ffff888058063e30 RCX: 0000000000080000
RDX: ffffc9000f1fd000 RSI: 0000000000030d0f RDI: 0000000000030d10
RBP: dffffc0000000000 R08: ffff8880b9133d7f R09: 1ffff110172267af
R10: dffffc0000000000 R11: ffffed10172267b0 R12: ffff888028d03b80
R13: ffff888058063e88 R14: ffff888058063e30 R15: 1ffff1100b00c7c7
FS: 00007f8d82f246c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c2b54d0 CR3: 000000001f9c9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
ovl_workdir_create+0x57f/0x630 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1376 [inline]
ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526
ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082
mount_nodev+0x52/0xe0 fs/super.c:1446
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8d84ceb819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8d82f24028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f8d84f65090 RCX: 00007f8d84ceb819
RDX: 0000200000000440 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f8d84d81c91 R08: 0000200000000080 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8d84f65128 R14: 00007f8d84f65090 R15: 00007ffc01e8bbc8
</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
syzbot
Apr 4, 2026, 4:47:35 PM (yesterday) Apr 4
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1369b5da580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/619dec96122b/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51216c...@syzkaller.appspotmail.com
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888057a5c590, owner = 0x0, curr 0xffff888059d98000, list empty
WARNING: CPU: 1 PID: 4394 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 4394 at kernel/locking/rwsem.c:1350 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 4394 Comm: syz.3.30 Not tainted syzkaller #0
RAX: bc87eeb58ac4d800 RBX: ffff888057a5c590 RCX: ffff888059d98000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
R13: ffff888057a5c5e8 R14: ffff888057a5c590 R15: 1ffff1100af4b8b3
FS: 00007f617a8016c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
RAX: ffffffffffffffda RBX: 00007f617b43a090 RCX: 00007f617b1c0819
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=51216c95e1873f4c4098
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f09516580000
dashboard link: https://syzkaller.appspot.com/bug?extid=51216c95e1873f4c4098
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51216c...@syzkaller.appspotmail.com
WARNING: CPU: 1 PID: 4394 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 4394 at kernel/locking/rwsem.c:1350 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 4394 Comm: syz.3.30 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Code: 44 d0 48 c7 c7 00 1b 2b 8a 48 c7 c6 c0 1d 2b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 53 1f 55 08 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 08 17 8a 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000340f790 EFLAGS: 00010296
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Code: 44 d0 48 c7 c7 00 1b 2b 8a 48 c7 c6 c0 1d 2b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 53 1f 55 08 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 08 17 8a 8d 80 e1 07 80 c1 03 38 c1
RAX: bc87eeb58ac4d800 RBX: ffff888057a5c590 RCX: ffff888059d98000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffff8880b9133d7f R09: 1ffff110172267af
R10: dffffc0000000000 R11: ffffed10172267b0 R12: 0000000000000000
R13: ffff888057a5c5e8 R14: ffff888057a5c590 R15: 1ffff1100af4b8b3
FS: 00007f617a8016c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001000 CR3: 0000000074cb2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
ovl_workdir_create+0x57f/0x630 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1376 [inline]
ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526
ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082
mount_nodev+0x52/0xe0 fs/super.c:1446
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f617b1c0819
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
ovl_workdir_create+0x57f/0x630 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1376 [inline]
ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526
ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082
mount_nodev+0x52/0xe0 fs/super.c:1446
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f617a801028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f617b43a090 RCX: 00007f617b1c0819
RDX: 0000200000000440 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f617b256c91 R08: 0000200000000080 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f617b43a128 R14: 00007f617b43a090 R15: 00007ffc0e88c248
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
syzbot
Apr 4, 2026, 6:18:25 PM (23 hours ago) Apr 4
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=102b4dda580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154dc1ca580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3f837c3edec6/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51216c...@syzkaller.appspotmail.com
WARNING: CPU: 0 PID: 4418 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 0 PID: 4418 at kernel/locking/rwsem.c:1350 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 0 PID: 4418 Comm: syz.0.37 Not tainted syzkaller #0
RAX: 05689041c175ab00 RBX: ffff88805f5ae310 RCX: ffff88802ae93b80
R10: dffffc0000000000 R11: ffffed10172067b0 R12: 0000000000000000
R13: ffff88805f5ae368 R14: ffff88805f5ae310 R15: 1ffff1100beb5c63
FS: 00007f608f5566c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
RAX: ffffffffffffffda RBX: 00007f609018f090 RCX: 00007f608ff15819
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=51216c95e1873f4c4098
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1425b5da580000
dashboard link: https://syzkaller.appspot.com/bug?extid=51216c95e1873f4c4098
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154dc1ca580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+51216c...@syzkaller.appspotmail.com
WARNING: CPU: 0 PID: 4418 at kernel/locking/rwsem.c:1350 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 0 PID: 4418 Comm: syz.0.37 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Code: 44 d0 48 c7 c7 00 1b 2b 8a 48 c7 c6 c0 1d 2b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 53 1f 55 08 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 08 17 8a 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000334f790 EFLAGS: 00010296
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1604
Code: 44 d0 48 c7 c7 00 1b 2b 8a 48 c7 c6 c0 1d 2b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 53 1f 55 08 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 08 17 8a 8d 80 e1 07 80 c1 03 38 c1
RAX: 05689041c175ab00 RBX: ffff88805f5ae310 RCX: ffff88802ae93b80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffff8880b9033d7f R09: 1ffff110172067af
R10: dffffc0000000000 R11: ffffed10172067b0 R12: 0000000000000000
R13: ffff88805f5ae368 R14: ffff88805f5ae310 R15: 1ffff1100beb5c63
FS: 00007f608f5566c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f47e281a000 CR3: 000000001f21e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
ovl_workdir_create+0x57f/0x630 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1376 [inline]
ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526
ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082
mount_nodev+0x52/0xe0 fs/super.c:1446
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f608ff15819
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
ovl_workdir_create+0x57f/0x630 fs/overlayfs/super.c:839
ovl_make_workdir fs/overlayfs/super.c:1376 [inline]
ovl_get_workdir+0x37c/0x1230 fs/overlayfs/super.c:1526
ovl_fill_super+0x1824/0x2a30 fs/overlayfs/super.c:2082
mount_nodev+0x52/0xe0 fs/super.c:1446
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f608f556028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f609018f090 RCX: 00007f608ff15819
RDX: 0000200000000440 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f608ffabc91 R08: 0000200000000080 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f609018f128 R14: 00007f609018f090 R15: 00007ffeb780fb18
Reply all
Reply to author
Forward
0 new messages