[v6.1] WARNING in jfs_rename
7 views
Skip to first unread message
syzbot
May 5, 2025, 12:58:27 AM5/5/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: b6736e03756f Linux 6.1.136
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17543b68580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1f31c8b4cdebec00
dashboard link: https://syzkaller.appspot.com/bug?extid=d90c9190e8b6dd57f963
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/562d684b3c71/disk-b6736e03.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16bb24a1b82d/vmlinux-b6736e03.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40b3e76f572a/bzImage-b6736e03.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d90c91...@syzkaller.appspotmail.com
loop4: detected capacity change from 0 to 32768
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4744 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4744 Comm: syz.4.72 Not tainted 6.1.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c0 07 00 00 be 08 00 00 00 e8 ab 7d eb ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 e5 08 9a ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90003cf78d0 EFLAGS: 00010283
RAX: ffffffff81e6babb RBX: ffff8880710d2930 RCX: 0000000000080000
RDX: ffffc9000e559000 RSI: 0000000000004c28 RDI: 0000000000004c29
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff940000c1d57
R10: fffff940000c1d57 R11: 1ffffd40000c1d56 R12: 1ffff1100e21a52f
R13: 1ffff9200079ef2c R14: ffff8880710d2978 R15: dffffc0000000000
FS: 00007fa7e1a3e6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2da1fffc CR3: 0000000058e40000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4874
do_renameat2+0x89d/0xc70 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+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa7e0b8e969
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:00007fa7e1a3e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fa7e0db5fa0 RCX: 00007fa7e0b8e969
RDX: 0000000000000000 RSI: 0000200000000780 RDI: 00002000000003c0
RBP: 00007fa7e0c10ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fa7e0db5fa0 R15: 00007ffcd3d4f138
</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: b6736e03756f Linux 6.1.136
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17543b68580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1f31c8b4cdebec00
dashboard link: https://syzkaller.appspot.com/bug?extid=d90c9190e8b6dd57f963
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/562d684b3c71/disk-b6736e03.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16bb24a1b82d/vmlinux-b6736e03.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40b3e76f572a/bzImage-b6736e03.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d90c91...@syzkaller.appspotmail.com
loop4: detected capacity change from 0 to 32768
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4744 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4744 Comm: syz.4.72 Not tainted 6.1.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c0 07 00 00 be 08 00 00 00 e8 ab 7d eb ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 e5 08 9a ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90003cf78d0 EFLAGS: 00010283
RAX: ffffffff81e6babb RBX: ffff8880710d2930 RCX: 0000000000080000
RDX: ffffc9000e559000 RSI: 0000000000004c28 RDI: 0000000000004c29
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff940000c1d57
R10: fffff940000c1d57 R11: 1ffffd40000c1d56 R12: 1ffff1100e21a52f
R13: 1ffff9200079ef2c R14: ffff8880710d2978 R15: dffffc0000000000
FS: 00007fa7e1a3e6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2da1fffc CR3: 0000000058e40000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4874
do_renameat2+0x89d/0xc70 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+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa7e0b8e969
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:00007fa7e1a3e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fa7e0db5fa0 RCX: 00007fa7e0b8e969
RDX: 0000000000000000 RSI: 0000200000000780 RDI: 00002000000003c0
RBP: 00007fa7e0c10ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fa7e0db5fa0 R15: 00007ffcd3d4f138
</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
May 5, 2025, 1:04:32 AM5/5/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 16fdf2c7111b Linux 5.15.181
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=114008f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1748ac0065c72647
dashboard link: https://syzkaller.appspot.com/bug?extid=39e82bbdc8c5c382597b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d8540163643f/disk-16fdf2c7.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/1a4c570bb8bc/vmlinux-16fdf2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4ed683eba5e/bzImage-16fdf2c7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4649 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4649 Comm: syz.4.82 Not tainted 5.15.181-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c8 07 00 00 be 08 00 00 00 e8 9b 12 ef ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 95 9d a9 ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
RSP: 0018:ffffc90002f7f8d0 EFLAGS: 00010283
RAX: ffffffff81ce207b RBX: ffff888060d3a930 RCX: 0000000000080000
RDX: ffffc9000df6a000 RSI: 0000000000006063 RDI: 0000000000006064
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff94000316dbf
R10: fffff94000316dbf R11: 1ffffd4000316dbe R12: 1ffff1100c1a752f
R13: 1ffff920005eff2c R14: ffff888060d3a978 R15: dffffc0000000000
FS: 00007f3e157ef6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6e9a38a338 CR3: 0000000058740000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4832
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
do_renameat2+0xa83/0xf70 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+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f3e17987969
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:00007f3e157ef038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f3e17baefa0 RCX: 00007f3e17987969
RDX: 0000000000000000 RSI: 0000200000000780 RDI: 00002000000003c0
RBP: 00007f3e17a09ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f3e17baefa0 R15: 00007ffc478d2218
syzbot
May 5, 2025, 1:21:38 AM5/5/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: b6736e03756f Linux 6.1.136
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10f008f4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f008f4580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/562d684b3c71/disk-b6736e03.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16bb24a1b82d/vmlinux-b6736e03.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40b3e76f572a/bzImage-b6736e03.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/5ef734c7beb7/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1581d0f4580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d90c91...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 32768
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4247 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4247 Comm: syz-executor396 Not tainted 6.1.136-syzkaller #0
RAX: ffffffff81e6babb RBX: ffff888070f21ff0 RCX: ffff88803027bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff94000134297
R10: fffff94000134297 R11: 1ffffd4000134296 R12: 1ffff1100e1e4407
R13: 1ffff92000786f2c R14: ffff888070f22038 R15: dffffc0000000000
FS: 000055557a13a380(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:00007ffe6b7ca1f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007ffe6b7ca3d8 RCX: 00007f0e14123639
R10: 00007ffe6b7ca0c0 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe6b7ca3c8 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: b6736e03756f Linux 6.1.136
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=1f31c8b4cdebec00
dashboard link: https://syzkaller.appspot.com/bug?extid=d90c9190e8b6dd57f963
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116c3b68580000
dashboard link: https://syzkaller.appspot.com/bug?extid=d90c9190e8b6dd57f963
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f008f4580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/562d684b3c71/disk-b6736e03.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16bb24a1b82d/vmlinux-b6736e03.xz
kernel image: https://storage.googleapis.com/syzbot-assets/40b3e76f572a/bzImage-b6736e03.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1581d0f4580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d90c91...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4247 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4247 Comm: syz-executor396 Not tainted 6.1.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c0 07 00 00 be 08 00 00 00 e8 ab 7d eb ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 e5 08 9a ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90003c378d0 EFLAGS: 00010293
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c0 07 00 00 be 08 00 00 00 e8 ab 7d eb ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 e5 08 9a ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RAX: ffffffff81e6babb RBX: ffff888070f21ff0 RCX: ffff88803027bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff94000134297
R10: fffff94000134297 R11: 1ffffd4000134296 R12: 1ffff1100e1e4407
R13: 1ffff92000786f2c R14: ffff888070f22038 R15: dffffc0000000000
FS: 000055557a13a380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff262379a8 CR3: 000000002bef7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4874
do_renameat2+0x89d/0xc70 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+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0e14123639
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4874
do_renameat2+0x89d/0xc70 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+0x4c/0xa0 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:00007ffe6b7ca1f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007ffe6b7ca3d8 RCX: 00007f0e14123639
RDX: 0000000000000000 RSI: 0000200000000780 RDI: 00002000000003c0
RBP: 00007f0e1419c610 R08: 0000000000006221 R09: 0000000000000000
R10: 00007ffe6b7ca0c0 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe6b7ca3c8 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
May 5, 2025, 1:24:30 AM5/5/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 16fdf2c7111b Linux 5.15.181
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d0c1cc580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14051f74580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d8540163643f/disk-16fdf2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1a4c570bb8bc/vmlinux-16fdf2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4ed683eba5e/bzImage-16fdf2c7.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/582c26163d31/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=10051f74580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39e82b...@syzkaller.appspotmail.com
WARNING: CPU: 0 PID: 4165 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 0 PID: 4165 Comm: syz-executor122 Not tainted 5.15.181-syzkaller #0
RAX: ffffffff81ce207b RBX: ffff888073b00430 RCX: ffff888020cb8000
R10: fffff94000111577 R11: 1ffffd4000111576 R12: 1ffff1100e76008f
R13: 1ffff920005bdf2c R14: ffff888073b00478 R15: dffffc0000000000
FS: 00005555583c2380(0000) GS:ffff8880b9000000(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:00007ffd89ae6678 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007ffd89ae6858 RCX: 00007f4b5c163639
R10: 00007ffd89ae6540 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffd89ae6848 R14: 0000000000000001 R15: 0000000000000001
HEAD commit: 16fdf2c7111b Linux 5.15.181
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=1748ac0065c72647
dashboard link: https://syzkaller.appspot.com/bug?extid=39e82bbdc8c5c382597b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149a8e6f980000
dashboard link: https://syzkaller.appspot.com/bug?extid=39e82bbdc8c5c382597b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14051f74580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d8540163643f/disk-16fdf2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1a4c570bb8bc/vmlinux-16fdf2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4ed683eba5e/bzImage-16fdf2c7.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=10051f74580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39e82b...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 32768
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4165 at fs/inode.c:332 drop_nlink+0xbb/0x100 fs/inode.c:332
Modules linked in:
CPU: 0 PID: 4165 Comm: syz-executor122 Not tainted 5.15.181-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c8 07 00 00 be 08 00 00 00 e8 9b 12 ef ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 95 9d a9 ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90002def8d0 EFLAGS: 00010293
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb c8 07 00 00 be 08 00 00 00 e8 9b 12 ef ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 95 9d a9 ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RAX: ffffffff81ce207b RBX: ffff888073b00430 RCX: ffff888020cb8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff94000111577
R10: fffff94000111577 R11: 1ffffd4000111576 R12: 1ffff1100e76008f
R13: 1ffff920005bdf2c R14: ffff888073b00478 R15: dffffc0000000000
FS: 00005555583c2380(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055c93d2caf28 CR3: 000000007a262000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4832
do_renameat2+0xa83/0xf70 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+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f4b5c163639
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_rename+0xbf8/0x16a0 fs/jfs/namei.c:1246
vfs_rename+0xbbf/0x10d0 fs/namei.c:4832
do_renameat2+0xa83/0xf70 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+0x4c/0xa0 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:00007ffd89ae6678 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007ffd89ae6858 RCX: 00007f4b5c163639
RDX: 0000000000000000 RSI: 0000200000000780 RDI: 00002000000003c0
RBP: 00007f4b5c1dc610 R08: 0000000000006221 R09: 0000000000000000
R10: 00007ffd89ae6540 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffd89ae6848 R14: 0000000000000001 R15: 0000000000000001
Reply all
Reply to author
Forward
0 new messages