[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6768b13d.050a0220.3a8527.0001.GAE@google.com>
Date: Sun, 22 Dec 2024 16:39:25 -0800
From: syzbot <syzbot+de6c4b3beb823e112ead@...kaller.appspotmail.com>
To: konishi.ryusuke@...il.com, linux-kernel@...r.kernel.org,
linux-nilfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [nilfs?] WARNING in nilfs_rename
Hello,
syzbot found the following issue on:
HEAD commit: aef25be35d23 hexagon: Disable constant extender optimizati..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11cab7e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=de6c4b3beb823e112ead
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-aef25be3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b51d6862d2de/vmlinux-aef25be3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cdb968bd31a4/bzImage-aef25be3.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+de6c4b3beb823e112ead@...kaller.appspotmail.com
loop0: detected capacity change from 0 to 4096
NILFS (loop0): invalid segment: Checksum error in segment payload
NILFS (loop0): trying rollback from an earlier position
NILFS (loop0): recovery complete
loop0: detected capacity change from 4096 to 64
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5319 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
Modules linked in:
CPU: 0 UID: 0 PID: 5319 Comm: syz.0.0 Not tainted 6.13.0-rc3-syzkaller-00044-gaef25be35d23 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:drop_nlink+0xc4/0x110 fs/inode.c:407
Code: bb 70 07 00 00 be 08 00 00 00 e8 c7 37 e7 ff 3e 48 ff 83 70 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 cc cc cc cc e8 5d cc 80 ff 90 <0f> 0b 90 eb 83 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 5c ff ff ff
RSP: 0018:ffffc9000d21f8f0 EFLAGS: 00010283
RAX: ffffffff821ea793 RBX: 1ffff1100a603834 RCX: 0000000000100000
RDX: ffffc9000e60a000 RSI: 0000000000000c56 RDI: 0000000000000c57
RBP: 0000000000000000 R08: ffffffff821ea713 R09: 1ffffffff2032f46
R10: dffffc0000000000 R11: fffffbfff2032f47 R12: ffff88805301c1a0
R13: ffff88804ced1050 R14: ffff88805301c158 R15: dffffc0000000000
FS: 00007f8bc463e6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8bc396c4c8 CR3: 00000000438e4000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_rename+0x7b0/0xb60 fs/nilfs2/namei.c:410
vfs_rename+0xbdb/0xf00 fs/namei.c:5067
do_renameat2+0xd94/0x13f0 fs/namei.c:5224
__do_sys_rename fs/namei.c:5271 [inline]
__se_sys_rename fs/namei.c:5269 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5269
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8bc3785d29
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:00007f8bc463e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f8bc3975fa0 RCX: 00007f8bc3785d29
RDX: 0000000000000000 RSI: 0000000020000b80 RDI: 0000000020001640
RBP: 00007f8bc3801a20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f8bc3975fa0 R15: 00007ffe7b8ea018
</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 syzkaller@...glegroups.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
Powered by blists - more mailing lists