From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "frank.li@vivo.com" <frank.li@vivo.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>
Subject: RE: [RFC] Should we consider to re-write HFS/HFS+ in Rust?
Date: Wed, 28 May 2025 16:16:58 +0000 [thread overview]
Message-ID: <1ab023f2e9822926ed63f79c7ad4b0fed4b5a717.camel@ibm.com> (raw)
In-Reply-To: <4fce1d92-4b49-413d-9ed1-c29eda0753fd@vivo.com>
On Wed, 2025-05-28 at 20:40 +0800, Yangtao Li wrote:
> +cc rust-for-linux
>
> 在 2025/5/28 07:39, Viacheslav Dubeyko 写道:
> > Hi Adrian, Yangtao,
> >
> > One idea crossed my mind recently. And this is about re-writing HFS/HFS+ in
> > Rust. It could be interesting direction but I am not sure how reasonable it
> > could be. From one point of view, HFS/HFS+ are not critical subsystems and we
> > can afford some experiments. From another point of view, we have enough issues
> > in the HFS/HFS+ code and, maybe, re-working HFS/HFS+ can make the code more
> > stable.
> >
> > I don't think that it's a good idea to implement the complete re-writing of the
> > whole driver at once. However, we need a some unification and generalization of
> > HFS/HFS+ code patterns in the form of re-usable code by both drivers. This re-
> > usable code can be represented as by C code as by Rust code. And we can
> > introduce this generalized code in the form of C and Rust at the same time. So,
> > we can re-write HFS/HFS+ code gradually step by step. My point here that we
> > could have C code and Rust code for generalized functionality of HFS/HFS+ and
> > Kconfig would define which code will be compiled and used, finally.
> >
> > How do you feel about this? And can we afford such implementation efforts?
>
> It must be a crazy idea! Honestly, I'm a fan of new things.
> If there is a clear path, I don't mind moving in that direction.
>
Why don't try even some crazy way. :)
> It seems that downstream already has rust implementations of puzzle and
> ext2 file systems. If I understand correctly, there is currently a lack
> of support for vfs and various infrastructure.
>
Yes, Rust implementation in kernel is slightly complicated topic. And I don't
suggest to implement the whole HFS/HFS+ driver at once. My idea is to start from
introduction of small Rust module that can implement some subset of HFS/HFS+
functionality that can be called by C code. It could look like a library that
HFS/HFS+ drivers can re-use. And we can have C and Rust "library" and people can
select what they would like to compile (C or Rust implementation).
> I'm not an expert on Rust, so it would be great if some Rust people
> could share their opinions.
>
>
I hope that Rust people would like the idea. :)
Thanks,
Slava.
next prev parent reply other threads:[~2025-05-28 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 23:39 [RFC] Should we consider to re-write HFS/HFS+ in Rust? Viacheslav Dubeyko
2025-05-28 7:11 ` John Paul Adrian Glaubitz
2025-05-28 16:10 ` Viacheslav Dubeyko
2025-05-28 12:40 ` Yangtao Li
2025-05-28 16:16 ` Viacheslav Dubeyko [this message]
2025-06-19 19:33 ` Benno Lossin
2025-06-19 20:22 ` Miguel Ojeda
2025-06-19 21:48 ` Viacheslav Dubeyko
2025-06-19 22:00 ` Benno Lossin
2025-06-20 8:17 ` Miguel Ojeda
2025-06-20 18:10 ` Viacheslav Dubeyko
2025-06-20 19:27 ` Miguel Ojeda
2025-06-19 21:39 ` Viacheslav Dubeyko
2025-06-19 22:24 ` Benno Lossin
2025-06-20 17:46 ` Viacheslav Dubeyko
2025-06-20 18:11 ` Miguel Ojeda
2025-06-21 22:38 ` Viacheslav Dubeyko
2025-06-22 7:48 ` Benno Lossin
2025-06-23 10:25 ` Miguel Ojeda
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=1ab023f2e9822926ed63f79c7ad4b0fed4b5a717.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=slava@dubeyko.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;
as well as URLs for NNTP newsgroup(s).