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: <tnofelm75pbsccdkulwpq7lkfz6wjmg4acrrvinkn6zzrkdxqi@dppnd4fge2tu>
Date: Thu, 30 Oct 2025 18:18:01 +0100
From: Jan Kara <jack@...e.cz>
To: Jeff Layton <jlayton@...nel.org>
Cc: Jori Koolstra <jkoolstra@...all.nl>, 
	Christian Brauner <brauner@...nel.org>, "skhan@...uxfoundation.org" <skhan@...uxfoundation.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 11:12:44, Jeff Layton wrote:
> On Thu, 2025-10-30 at 15:09 +0100, Jori Koolstra wrote:
> > > You're quite right though that userland replacements will need to meet
> > > some criteria before we can rip out the in-kernel versions. This might
> > > be a good discussion topic for next year's LSF/MM!
> > 
> > Would an in-tree but out of kernel implementation be an idea? Like how
> > kselftest is integrated in the code, even though most of that also takes
> > place in userland. That would guarantee a level of support, at least for
> > the time being. I could take the code, verify it, and write some tests
> > for in selftest.
> 
> That's not a bad idea. We already have some userland code in the kernel
> tree (the tools/ directory comes to mind). A directory with replacement
> FUSE drivers for in-kernel filesystems could be a reasonable thing to
> add. Anything we keep in-tree will need to be GPL-compatible though.

Yes, I kind of like that idea too. I think we could maybe take the existing
in-kernel minix driver and morph it into a FUSE driver which would deal
with the licensing as well.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ