public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+320c57a47bdabc1f294b@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, jkoolstra@xs4all.nl,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 surajsonawane0215@gmail.com, syzkaller-bugs@googlegroups.com,
	tytso@mit.edu,  viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] WARNING in minix_unlink
Date: Sun, 11 Jan 2026 20:24:03 -0800	[thread overview]
Message-ID: <69647763.050a0220.eaf7.0084.GAE@google.com> (raw)
In-Reply-To: <6740d107.050a0220.3c9d61.0195.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 009a2ba40303cb1e3556c41233338e609ac509ea
Author: Jori Koolstra <jkoolstra@xs4all.nl>
Date:   Tue Nov 4 14:30:05 2025 +0000

    Fix a drop_nlink warning in minix_rename

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=152d65fa580000
start commit:   c0c9379f235d Merge tag 'usb-6.16-rc1' of git://git.kernel...
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=d9ebb51ccc2ec42f
dashboard link: https://syzkaller.appspot.com/bug?extid=320c57a47bdabc1f294b
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10f409d4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1044ec0c580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Fix a drop_nlink warning in minix_rename

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2026-01-12  4:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 18:44 [syzbot] [fs?] WARNING in minix_unlink syzbot
2024-11-24 19:13 ` Suraj Sonawane
2024-11-24 19:41   ` syzbot
2024-11-24 19:47     ` Al Viro
2024-11-24 20:10       ` Al Viro
2024-11-25  3:00         ` Theodore Ts'o
2024-11-25  5:49           ` Suraj Sonawane
2024-11-25  5:47         ` Suraj Sonawane
2026-01-12  4:24 ` syzbot [this message]
2026-01-12 11:50   ` Jan Kara

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=69647763.050a0220.eaf7.0084.GAE@google.com \
    --to=syzbot+320c57a47bdabc1f294b@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jkoolstra@xs4all.nl \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=surajsonawane0215@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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