From: syzbot <syzbot+f6c7e1f1809f235eeb90@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING in nilfs_rename (2)
Date: Fri, 25 Sep 2026 08:53:01 -0700 [thread overview]
Message-ID: <6ab698dd.80e1c6cc.1e8e5f.0039.GAE@google.com> (raw)
In-Reply-To: <20260926.003610.1086231564499039984.konishi.ryusuke@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in nilfs_rename
------------[ cut here ]------------
inode->i_nlink == 0
WARNING: fs/inode.c:408 at drop_nlink+0xc5/0x110 fs/inode.c:408, CPU#0: syz.0.17/5904
Modules linked in:
CPU: 0 UID: 0 PID: 5904 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:drop_nlink+0xc5/0x110 fs/inode.c:408
Code: a8 07 00 00 be 08 00 00 00 e8 47 6b e4 ff f0 48 ff 83 a8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 cc cc cc cc cc e8 3c 13 73 ff 90 <0f> 0b 90 eb 81 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 5b ff ff ff
RSP: 0018:ffffc900051679f0 EFLAGS: 00010293
RAX: ffffffff825406c4 RBX: ffff888042e04d70 RCX: ffff888000ae0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff9055877f R09: 1ffffffff20ab0ef
R10: dffffc0000000000 R11: fffffbfff20ab0f0 R12: 1ffff110085c09b7
R13: ffff888042e05990 R14: ffff888042e04db8 R15: dffffc0000000000
FS: 00007f1c7f8f66c0(0000) GS:ffff88808c5a0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f80b5775a10 CR3: 0000000033897000 CR4: 0000000000352ef0
Call Trace:
<TASK>
nilfs_rename+0x4b0/0x8a0 fs/nilfs2/namei.c:418
vfs_rename+0xbd9/0xef0 fs/namei.c:6208
filename_renameat2+0x533/0x9a0 fs/namei.c:6326
__do_sys_renameat2 fs/namei.c:6355 [inline]
__se_sys_renameat2+0x5a/0x2c0 fs/namei.c:6350
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x155/0x510 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1c7e99aeb9
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:00007f1c7f8f6028 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f1c7ec16180 RCX: 00007f1c7e99aeb9
RDX: 0000000000000006 RSI: 00002000000000c0 RDI: 0000000000000007
RBP: 00007f1c7ea08c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000200000000100 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1c7ec16218 R14: 00007f1c7ec16180 R15: 00007ffc83c7ff08
</TASK>
Tested on:
commit: 89a31299 Merge tag 'cifs-fixes-7.3-rc2' of https://git..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16c0fc5e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=db6ce8c8614a5a8f
dashboard link: https://syzkaller.appspot.com/bug?extid=f6c7e1f1809f235eeb90
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=139f7c5e580000
next parent reply other threads:[~2026-09-25 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260926.003610.1086231564499039984.konishi.ryusuke@gmail.com>
2026-09-25 15:53 ` syzbot [this message]
2025-08-22 8:08 syzbot
2025-10-13 9:18 ` syzbot
2025-10-13 9:59 ` Ryusuke Konishi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ab698dd.80e1c6cc.1e8e5f.0039.GAE@google.com \
--to=syzbot+f6c7e1f1809f235eeb90@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®