[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <844014437.2785230.1764107527482@kpc.webmail.kpnmail.nl>
Date: Tue, 25 Nov 2025 22:52:07 +0100 (CET)
From: Jori Koolstra <jkoolstra@...all.nl>
To: Jan Kara <jack@...e.cz>
Cc: Christian Brauner <brauner@...nel.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Taotao Chen <chentaotao@...iglobal.com>,
Shuah Khan <skhan@...uxfoundation.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] minix: calculate s_firstdatazone to support more
inodes
Hello Jan,
>
> This changelog misses explanation why handling s_firstdatazone == 0 is a
> good idea in the first place. Is it somehow situation present in real
> filesystems? If not then then why bother? More flexibility in accepting
> garbage always means more trouble down the road :), we've learned this
> lesson several times.
>
I believe that the Minix OS implementation of mfs supports it:
https://github.com/Stichting-MINIX-Research-Foundation/minix/
blob/4db99f4012570a577414fe2a43697b2f239b699e/minix/usr.sbin/
mkfs.mfs/mkfs.c#L659
But I understand your concern. Perhaps we should not make too many changes
to minix as discussed before. I would really like to work on a FUSE driver
for it, but am a bit stuck. I've discussed this with Shuah and she encourages
me to do it. However, I need to have some help to vet my idea on how to approach
it. She would have helped me but told me she is not an fs expert. Can I ask you
some questions to see if my approach is at least sensible? It would make a huge
difference to me. Of course, I also understand if you have no time for this.
Thanks,
Jori.
Powered by blists - more mailing lists