linux-kernel - Re: [PATCH] Add error handling to minix filesystem similar to ext4

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ebc2e6ptdbfqrd4vwgswmqzuzm5joztd2jfg2cvq7wdxhtnjb@f52arbgipszs>
Date: Thu, 30 Oct 2025 18:12:11 +0100
From: Jan Kara <jack@...e.cz>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: Jeff Layton <jlayton@...nel.org>, Jori Koolstra <jkoolstra@...all.nl>, 
	Christian Brauner <brauner@...nel.org>, Khalid Aziz <khalid@...nel.org>, 
	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, Jan Kara <jack@...e.cz>, Taotao Chen <chentaotao@...iglobal.com>, 
	NeilBrown <neil@...wn.name>, linux-kernel@...r.kernel.org, 
	syzbot+4e49728ec1cbaf3b91d2@...kaller.appspotmail.com
Subject: Re: [PATCH] Add error handling to minix filesystem similar to ext4

On Thu 30-10-25 09:44:40, Shuah Khan wrote:
> On 10/30/25 09:12, Jeff Layton wrote:
> > On Thu, 2025-10-30 at 15:09 +0100, Jori Koolstra wrote:
> > > And there is still the issue of what we do for the syzbot bugs until a
> > > more permanent solution is achieved.
> > > 
> > 
> > Yeah, that's a different issue.  Most likely we'll need to fix those in
> > the near term. Replacing minix.ko with a FUSE fs will take time
> > (years), even once we have a new driver in hand.
> Does this mean Jori can work on fixing these while replacing minix.ko
> with fuse progresses?

Yes, we generally accept fixes to syzbot bugs even for old filesystems.
It's just that for these old filesystems there's limited enthusiasm to
accept large-scale changes just to fix some odd syzbot issue. But luckily
most of the syzbot bugs are usually fixed just by proper input validation
which isn't usually very intrusive.

> > We'll need to mark the old driver deprecated and then wait a few
> > releases before we can rip it out.
> Jori could work on patches for deprecating perhaps?

He could but deprecation is pretty easy - just print a notice about
deprecation to the kernel log on mount, update MAINTAINERS file etc. But
more interesting is making sure the userspace driver has feature parity
with the kernel driver before we start the kernel driver deprecation.

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