[v6.1] WARNING in udf_rename
5 views
Skip to first unread message
syzbot
Dec 11, 2024, 1:39:25 AM12/11/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=132d3544580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
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+72f20d...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9660 at fs/inode.c:332 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 0 PID: 9660 Comm: syz.0.801 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 49 8b 1e 48 8d bb c0 07 00 00 be 08 00 00 00 e8 3b f1 e9 ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 65 66 92 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc900042e7650 EFLAGS: 00010287
RAX: ffffffff81f8358b RBX: 1ffff1100aa0c1ce RCX: 0000000000080000
RDX: ffffc9001b50d000 RSI: 0000000000013217 RDI: 0000000000013218
RBP: 0000000000000000 R08: ffffffff81f8350f R09: fffffbfff2249889
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888055060e70
R13: 0000000067593363 R14: ffff888055060e28 R15: dffffc0000000000
FS: 00007f3c8105e6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30f15ff8 CR3: 000000005ecf6000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2582 [inline]
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4874
do_renameat2+0xde0/0x1440 fs/namei.c:5027
__do_sys_rename fs/namei.c:5073 [inline]
__se_sys_rename fs/namei.c:5071 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5071
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:0x7f3c8017ff19
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:00007f3c8105e058 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f3c80345fa0 RCX: 00007f3c8017ff19
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007f3c801f3cc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f3c80345fa0 R15: 00007ffdc3aecc78
</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: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=132d3544580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
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+72f20d...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9660 at fs/inode.c:332 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 0 PID: 9660 Comm: syz.0.801 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 49 8b 1e 48 8d bb c0 07 00 00 be 08 00 00 00 e8 3b f1 e9 ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 65 66 92 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc900042e7650 EFLAGS: 00010287
RAX: ffffffff81f8358b RBX: 1ffff1100aa0c1ce RCX: 0000000000080000
RDX: ffffc9001b50d000 RSI: 0000000000013217 RDI: 0000000000013218
RBP: 0000000000000000 R08: ffffffff81f8350f R09: fffffbfff2249889
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888055060e70
R13: 0000000067593363 R14: ffff888055060e28 R15: dffffc0000000000
FS: 00007f3c8105e6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30f15ff8 CR3: 000000005ecf6000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2582 [inline]
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4874
do_renameat2+0xde0/0x1440 fs/namei.c:5027
__do_sys_rename fs/namei.c:5073 [inline]
__se_sys_rename fs/namei.c:5071 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5071
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:0x7f3c8017ff19
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:00007f3c8105e058 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f3c80345fa0 RCX: 00007f3c8017ff19
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007f3c801f3cc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f3c80345fa0 R15: 00007ffdc3aecc78
</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
Dec 11, 2024, 2:06:23 AM12/11/24
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 0a51d2d4527b Linux 5.15.173
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10433544580000
kernel config: https://syzkaller.appspot.com/x/.config?x=48dad5136d11d5fc
dashboard link: https://syzkaller.appspot.com/bug?extid=99bb36d7a3ea562b950e
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/df502ed32946/disk-0a51d2d4.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/a6f49f24ceaa/vmlinux-0a51d2d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f45db4b68abf/bzImage-0a51d2d4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4461 at fs/inode.c:307 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 0 PID: 4461 Comm: syz.4.52 Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:307
Code: 49 8b 1e 48 8d bb c8 07 00 00 be 08 00 00 00 e8 bb a3 ed ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 c5 c9 a3 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90003187650 EFLAGS: 00010283
RAX: ffffffff81dca9db RBX: 1ffff1100be07034 RCX: 0000000000080000
RDX: ffffc9000dad9000 RSI: 00000000000090b4 RDI: 00000000000090b5
RBP: 0000000000000000 R08: ffffffff81dca95f R09: fffffbfff213104d
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88805f0381a0
R13: 00000000675939d4 R14: ffff88805f038158 R15: dffffc0000000000
FS: 00007fb70d7436c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056243b43d250 CR3: 000000001c341000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2505 [inline]
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4832
do_renameat2+0xe0f/0x1700 fs/namei.c:4985
__do_sys_rename fs/namei.c:5031 [inline]
__se_sys_rename fs/namei.c:5029 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5029
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:0x7fb70f8ccf19
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:00007fb70d743058 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fb70fa92fa0 RCX: 00007fb70f8ccf19
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007fb70f940cc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fb70fa92fa0 R15: 00007ffe11a1ea38
syzbot
Dec 11, 2024, 2:06:24 AM12/11/24
to syzkaller...@googlegroups.com
syzbot has found a reproducer for 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=1728b8f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13fcc20f980000
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
mounted in repro: https://storage.googleapis.com/syzbot-assets/f660ae2ce5b4/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+72f20d...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'Li uxUDF', timestamp 2022/11/22 14:59 (1000)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4247 at fs/inode.c:332 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 0 PID: 4247 Comm: syz-executor128 Not tainted 6.1.119-syzkaller #0
RAX: ffffffff81f8358b RBX: 1ffff1100e1741ce RCX: ffff888024be8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81f8350f R09: fffffbfff2249866
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888070ba0e70
R13: 00000000675939bf R14: ffff888070ba0e28 R15: dffffc0000000000
FS: 0000555579e30380(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd9ce67d48 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f78be963879
RDX: 00007f78be963879 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007f78be9d7610 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffd9ce67f18 R14: 0000000000000001 R15: 0000000000000001
</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: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1327db30580000
dashboard link: https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13fcc20f980000
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+72f20d...@syzkaller.appspotmail.com
UDF-fs: INFO Mounting volume 'Li uxUDF', timestamp 2022/11/22 14:59 (1000)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4247 at fs/inode.c:332 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 0 PID: 4247 Comm: syz-executor128 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 49 8b 1e 48 8d bb c0 07 00 00 be 08 00 00 00 e8 3b f1 e9 ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 65 66 92 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90003a87650 EFLAGS: 00010293
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 49 8b 1e 48 8d bb c0 07 00 00 be 08 00 00 00 e8 3b f1 e9 ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 65 66 92 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RAX: ffffffff81f8358b RBX: 1ffff1100e1741ce RCX: ffff888024be8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81f8350f R09: fffffbfff2249866
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888070ba0e70
R13: 00000000675939bf R14: ffff888070ba0e28 R15: dffffc0000000000
FS: 0000555579e30380(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000560d3f77e680 CR3: 000000007ad3c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2582 [inline]
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4874
do_renameat2+0xde0/0x1440 fs/namei.c:5027
__do_sys_rename fs/namei.c:5073 [inline]
__se_sys_rename fs/namei.c:5071 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5071
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:0x7f78be963879
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2582 [inline]
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4874
do_renameat2+0xde0/0x1440 fs/namei.c:5027
__do_sys_rename fs/namei.c:5073 [inline]
__se_sys_rename fs/namei.c:5071 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5071
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
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd9ce67d48 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f78be963879
RDX: 00007f78be963879 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007f78be9d7610 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffd9ce67f18 R14: 0000000000000001 R15: 0000000000000001
</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
Dec 11, 2024, 2:32:28 AM12/11/24
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=178fdb30580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12333544580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df502ed32946/disk-0a51d2d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a6f49f24ceaa/vmlinux-0a51d2d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f45db4b68abf/bzImage-0a51d2d4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/1b0cc70f0ea0/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+99bb36...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4160 at fs/inode.c:307 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 1 PID: 4160 Comm: syz-executor307 Not tainted 5.15.173-syzkaller #0
RAX: ffffffff81dca9db RBX: 1ffff1100e2f21ce RCX: ffff888024d13b80
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888071790e70
R13: 0000000067593fcb R14: ffff888071790e28 R15: dffffc0000000000
FS: 000055556e4e5380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeaa3f01b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f46dfe45879
RDX: 00007f46dfe45879 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007f46dfeb9610 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffeaa3f0388 R14: 0000000000000001 R15: 0000000000000001
HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=48dad5136d11d5fc
dashboard link: https://syzkaller.appspot.com/bug?extid=99bb36d7a3ea562b950e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1732c20f980000
dashboard link: https://syzkaller.appspot.com/bug?extid=99bb36d7a3ea562b950e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12333544580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df502ed32946/disk-0a51d2d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a6f49f24ceaa/vmlinux-0a51d2d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f45db4b68abf/bzImage-0a51d2d4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+99bb36...@syzkaller.appspotmail.com
------------[ cut here ]------------
Modules linked in:
CPU: 1 PID: 4160 Comm: syz-executor307 Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:307
Code: 49 8b 1e 48 8d bb c8 07 00 00 be 08 00 00 00 e8 bb a3 ed ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 c5 c9 a3 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc900011df650 EFLAGS: 00010293
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:307
Code: 49 8b 1e 48 8d bb c8 07 00 00 be 08 00 00 00 e8 bb a3 ed ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 c5 c9 a3 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RAX: ffffffff81dca9db RBX: 1ffff1100e2f21ce RCX: ffff888024d13b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81dca95f R09: fffffbfff213103b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888071790e70
R13: 0000000067593fcb R14: ffff888071790e28 R15: dffffc0000000000
FS: 000055556e4e5380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055752affd9d0 CR3: 0000000024b1f000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2505 [inline]
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4832
do_renameat2+0xe0f/0x1700 fs/namei.c:4985
__do_sys_rename fs/namei.c:5031 [inline]
__se_sys_rename fs/namei.c:5029 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5029
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:0x7f46dfe45879
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2505 [inline]
udf_rename+0xa46/0xdd0 fs/udf/namei.c:850
vfs_rename+0xd32/0x10f0 fs/namei.c:4832
do_renameat2+0xe0f/0x1700 fs/namei.c:4985
__do_sys_rename fs/namei.c:5031 [inline]
__se_sys_rename fs/namei.c:5029 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5029
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
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeaa3f01b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f46dfe45879
RDX: 00007f46dfe45879 RSI: 0000000020000080 RDI: 0000000020000400
RBP: 00007f46dfeb9610 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffeaa3f0388 R14: 0000000000000001 R15: 0000000000000001
syzbot
Jan 14, 2025, 7:24:04 AM1/14/25
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:
commit 6756af923e06aa33ad8894aaecbf9060953ba00f
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Tue Nov 26 11:55:12 2024 +0000
udf: Verify inode link counts before performing rename
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=168201f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11daccdf980000
Please keep in mind that other backports might be required as well.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit 6756af923e06aa33ad8894aaecbf9060953ba00f
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Tue Nov 26 11:55:12 2024 +0000
udf: Verify inode link counts before performing rename
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=168201f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144eb3e8580000
dashboard link: https://syzkaller.appspot.com/bug?extid=72f20dcde8dd7e4a788a
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11daccdf980000
Please keep in mind that other backports might be required as well.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Feb 6, 2025, 6:41:05 AM2/6/25
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:
commit 6756af923e06aa33ad8894aaecbf9060953ba00f
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Tue Nov 26 11:55:12 2024 +0000
udf: Verify inode link counts before performing rename
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155a80e4580000
commit 6756af923e06aa33ad8894aaecbf9060953ba00f
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Tue Nov 26 11:55:12 2024 +0000
udf: Verify inode link counts before performing rename
kernel config: https://syzkaller.appspot.com/x/.config?x=48dad5136d11d5fc
dashboard link: https://syzkaller.appspot.com/bug?extid=99bb36d7a3ea562b950e
dashboard link: https://syzkaller.appspot.com/bug?extid=99bb36d7a3ea562b950e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1732c20f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12333544580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12333544580000
syzbot
Nov 24, 2025, 2:06:14 AM11/24/25
to syzkaller...@googlegroups.com
For archival purposes, forwarding an incoming command email to
syzkaller...@googlegroups.com.
***
Subject: WARNING in udf_rename
Author: hsuk...@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-6.1.y
syzkaller...@googlegroups.com.
***
Subject: WARNING in udf_rename
Author: hsuk...@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-6.1.y
syzbot
Nov 24, 2025, 2:23:36 AM11/24/25
to syzkaller...@googlegroups.com
Subject: Re: WARNING in udf_rename
>
> On Mon, Nov 24, 2025 at 12:51 PM sukrut heroorkar <hsuk...@gmail.com> wrote:
> >
> >
Author: hsuk...@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-6.1.y
On Mon, Nov 24, 2025 at 12:52 PM sukrut heroorkar <hsuk...@gmail.com> wrote:
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-6.1.y
>
> On Mon, Nov 24, 2025 at 12:51 PM sukrut heroorkar <hsuk...@gmail.com> wrote:
> >
> >
syzbot
Nov 24, 2025, 3:20:19 AM11/24/25
to syzkaller...@googlegroups.com
Subject: WARNING in udf_rename
syzbot
Nov 24, 2025, 4:32:39 AM11/24/25
to syzkaller...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages