linux-kernel - Re: [PATCH] Fix a drop_nlink warning in minix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <l3x2jcya7en5ow5l5u3z5ukxr6ilp7snecm5i42zs4ci2t25j6@tesly72cat3d>
Date: Tue, 4 Nov 2025 08:42:04 +0100
From: Jan Kara <jack@...e.cz>
To: Jori Koolstra <jkoolstra@...all.nl>
Cc: Jan Kara <jack@...e.cz>, Christian Brauner <brauner@...nel.org>, 
	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, Taotao Chen <chentaotao@...iglobal.com>, 
	Jeff Layton <jlayton@...nel.org>, NeilBrown <neil@...wn.name>, linux-kernel@...r.kernel.org, 
	syzbot+4e49728ec1cbaf3b91d2@...kaller.appspotmail.com
Subject: Re: [PATCH] Fix a drop_nlink warning in minix_rmdir

Hello Jori!

On Mon 03-11-25 14:21:48, Jori Koolstra wrote:
> > Looks good, just one nit below. With that fixed feel free to add:
> > 
> > Reviewed-by: Jan Kara <jack@...e.cz>
> 
> Will do. Question: I have fixed another syzbot bug report in minix_rename/unlink
> and posted the patch. I figured that because they target different syzbot
> reports, they should be separate patches. However, I forgot to add the
> EFSCORRUPTED define in that patch (but did include it in the #syz test). What is
> the best way to rectify that and add your suggestion to this patch? Or should it
> be a single patch, or a series? I want to cause as little work as possible for
> you and other maintainers.

The most natural would be to submit these two patches in a single series
since they are actually related.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR