mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
	"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
	Khalid Aziz <khalid@kernel.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Taotao Chen <chentaotao@didiglobal.com>,
	NeilBrown <neil@brown.name>,
	linux-kernel@vger.kernel.org,
	syzbot+4e49728ec1cbaf3b91d2@syzkaller.appspotmail.com
Subject: Re: [PATCH] Add error handling to minix filesystem similar to ext4
Date: Fri, 31 Oct 2025 00:42:48 +0100 (CET)	[thread overview]
Message-ID: <1767594126.3216238.1761867768351@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <tnofelm75pbsccdkulwpq7lkfz6wjmg4acrrvinkn6zzrkdxqi@dppnd4fge2tu>


> 
> 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.
> 

By now I am quite comfortable with the in-kernel implementation as it exists.
The parts that I understand less are about how exactly the data from the
device ends up in the right place in memory and how address_space and folios
are built up for it. But these are precisely the parts that are not too
relevant for a userspace driver. So, I would be very happy to work on a GPL
FUSE driver for minix and get it to functional parity for all versions v1-v3.
After that, and when all the available tests run well, we can start the
deprecation process.

I think this would be a great opportunity for me to learn and contribute
something non-trivial, but that is still within my current level of ability.
Shuah has also encouraged me to proceed on this track. However, since this
is more than a couple of days work for me (for one I have to study the FUSE
API), it would be helpful if I can get a sense of whether there is a
reasonable chance for such work to be eventually included upstream. Of
course, only IF it functions according to the criteria set out. I am not
looking for guarantees, because I understand that is not how Linux
development works, but just a sense of how the community feels about this.
So far I have seen quite favorable responses, but I am too unfamiliar with
the development process to understand how this may play out.

Thanks again Jan and Jeff for your patient replies.

Jori

  reply	other threads:[~2025-10-30 23:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 20:58 Jori Koolstra
2025-10-30 10:59 ` Jan Kara
2025-10-30 11:18   ` Tetsuo Handa
2025-10-30 11:35     ` Jan Kara
2025-10-30 12:22   ` Jori Koolstra
2025-10-30 12:59     ` Jeff Layton
2025-10-30 13:31       ` Jori Koolstra
2025-10-30 13:43         ` Jeff Layton
2025-10-30 14:09           ` Jori Koolstra
2025-10-30 15:12             ` Jeff Layton
2025-10-30 15:44               ` Shuah Khan
2025-10-30 17:12                 ` Jan Kara
2025-10-30 17:40                 ` Jeff Layton
2025-10-30 17:18               ` Jan Kara
2025-10-30 23:42                 ` Jori Koolstra [this message]
2025-10-30 17:22           ` Jan Kara
2025-10-30 18:00             ` Jeff Layton
2025-10-30 15:38         ` Shuah Khan
2025-10-30 17:01     ` Jan Kara
2025-10-30 23:16       ` Jori Koolstra
2025-10-31 15:38         ` Jan Kara
2025-11-01 20:27 ` kernel test robot

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=1767594126.3216238.1761867768351@kpc.webmail.kpnmail.nl \
    --to=jkoolstra@xs4all.nl \
    --cc=brauner@kernel.org \
    --cc=chentaotao@didiglobal.com \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=khalid@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+4e49728ec1cbaf3b91d2@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®