All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 02 Nov 2025 08:12:03 -0800	[thread overview]
Message-ID: <690782d3.050a0220.29fc44.0026.GAE@google.com> (raw)
In-Reply-To: <857840797.3476876.1762098642816@kpc.webmail.kpnmail.nl>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in minix_unlink

------------[ cut here ]------------
WARNING: CPU: 1 PID: 6330 at fs/inode.c:417 drop_nlink+0xc5/0x110 fs/inode.c:417
Modules linked in:
CPU: 1 UID: 0 PID: 6330 Comm: syz-executor 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 47 dc e7 ff f0 48 ff 83 70 07 00 00 5b 41 5c 41 5e 41 5f 5d e9 d2 6f f2 08 cc e8 7c cf 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:ffffc90002f27c50 EFLAGS: 00010293
RAX: ffffffff823cd494 RBX: ffff8880741d9a58 RCX: ffff888026821e40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff8f5a5977 R09: 1ffffffff1eb4b2e
R10: dffffc0000000000 R11: fffffbfff1eb4b2f R12: 1ffff1100e83b354
R13: ffffea0001c8f900 R14: ffff8880741d9aa0 R15: dffffc0000000000
FS:  00005555875cf500(0000) GS:ffff8881264c8000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555587602688 CR3: 00000000336f8000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 inode_dec_link_count include/linux/fs.h:2655 [inline]
 minix_unlink+0x1de/0x290 fs/minix/namei.c:157
 vfs_unlink+0x394/0x650 fs/namei.c:4673
 do_unlinkat+0x345/0x560 fs/namei.c:4737
 __do_sys_unlink fs/namei.c:4783 [inline]
 __se_sys_unlink fs/namei.c:4781 [inline]
 __x64_sys_unlink+0x47/0x50 fs/namei.c:4781
 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:0x7f7a5978ded7
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 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:00007ffdec37a198 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7a5978ded7
RDX: 00007ffdec37a1c0 RSI: 00007ffdec37a250 RDI: 00007ffdec37a250
RBP: 00007ffdec37a250 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffdec37b340
R13: 00007f7a59810925 R14: 000000000001ff83 R15: 00007ffdec37d500
 </TASK>


Tested on:

commit:         691d401c Merge tag 'spi-fix-v6.18-rc3' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16fda342580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=824b00f06adfda3c
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=133f9012580000


       reply	other threads:[~2025-11-02 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <857840797.3476876.1762098642816@kpc.webmail.kpnmail.nl>
2025-11-02 16:12 ` 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] <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] <1558240174.1174599.1760455481777@kpc.webmail.kpnmail.nl>
2025-10-14 15:50 ` 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=690782d3.050a0220.29fc44.0026.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.