From: syzbot <syzbot+a65e824272c5f741247d@syzkaller.appspotmail.com>
To: jkoolstra@xs4all.nl, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] WARNING in minix_rename
Date: Tue, 14 Oct 2025 08:50:02 -0700 [thread overview]
Message-ID: <68ee712a.050a0220.1186a4.0034.GAE@google.com> (raw)
In-Reply-To: <1558240174.1174599.1760455481777@kpc.webmail.kpnmail.nl>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in minix_rename
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6502 at fs/inode.c:417 drop_nlink+0xc5/0x110 fs/inode.c:417
Modules linked in:
CPU: 1 UID: 0 PID: 6502 Comm: syz.1.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:drop_nlink+0xc5/0x110 fs/inode.c:417
Code: 70 07 00 00 be 08 00 00 00 e8 57 df e7 ff f0 48 ff 83 70 07 00 00 5b 41 5c 41 5e 41 5f 5d e9 92 ba f1 08 cc e8 9c d7 82 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:ffffc90003cefa30 EFLAGS: 00010293
RAX: ffffffff823cc9d4 RBX: ffff8880560b0fe8 RCX: ffff888058c0dac0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff8f5a6577 R09: 1ffffffff1eb4cae
R10: dffffc0000000000 R11: fffffbfff1eb4caf R12: 1ffff1100ac16206
R13: 0000000000000000 R14: ffff8880560b1030 R15: dffffc0000000000
FS: 00007fc01f0c26c0(0000) GS:ffff8881264ca000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc01f0c1f98 CR3: 0000000032b16000 CR4: 00000000003526f0
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2655 [inline]
minix_rename+0x3cf/0x700 fs/minix/namei.c:228
vfs_rename+0xb34/0xe80 fs/namei.c:5216
do_renameat2+0x6a2/0xa50 fs/namei.c:5364
__do_sys_rename fs/namei.c:5411 [inline]
__se_sys_rename fs/namei.c:5409 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5409
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc01e18e929
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:00007fc01f0c2038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fc01e3b6080 RCX: 00007fc01e18e929
RDX: 0000000000000000 RSI: 00002000000001c0 RDI: 0000200000001980
RBP: 00007fc01e210b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fc01e3b6080 R15: 00007ffc5451e3e8
</TASK>
Tested on:
commit: 3a866087 Linux 6.18-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17642c58580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4dacb8e711c7e98e
dashboard link: https://syzkaller.appspot.com/bug?extid=a65e824272c5f741247d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=126705e2580000
next parent reply other threads:[~2025-10-14 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1558240174.1174599.1760455481777@kpc.webmail.kpnmail.nl>
2025-10-14 15:50 ` syzbot [this message]
[not found] <196626359.3484070.1762102724022@kpc.webmail.kpnmail.nl>
2025-11-02 17:27 ` [syzbot] [fs?] WARNING in minix_rename syzbot
[not found] <857840797.3476876.1762098642816@kpc.webmail.kpnmail.nl>
2025-11-02 16:12 ` syzbot
[not found] <74426506.3493273.1762095398029@kpc.webmail.kpnmail.nl>
2025-11-02 15:20 ` syzbot
[not found] <75345955.3491850.1762094510741@kpc.webmail.kpnmail.nl>
2025-11-02 14:52 ` syzbot
[not found] <657566348.996550.1760362721717@kpc.webmail.kpnmail.nl>
2025-10-13 13:59 ` syzbot
[not found] <20250718105849.484227-1-richard120310@gmail.com>
2025-07-18 11:19 ` syzbot
2025-06-24 17:02 syzbot
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=68ee712a.050a0220.1186a4.0034.GAE@google.com \
--to=syzbot+a65e824272c5f741247d@syzkaller.appspotmail.com \
--cc=jkoolstra@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.