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: <aXe9nhAsK2lzOoxY@casper.infradead.org>
Date: Mon, 26 Jan 2026 19:16:46 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Cong Wang <cwang@...tikernel.io>
Cc: Gao Xiang <hsiangkao@...ux.alibaba.com>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, Cong Wang <xiyou.wangcong@...il.com>,
	multikernel@...ts.linux.dev
Subject: Re: [ANNOUNCE] DAXFS: A zero-copy, dmabuf-friendly filesystem for
 shared memory

On Mon, Jan 26, 2026 at 09:38:23AM -0800, Cong Wang wrote:
> If you are interested in adding multikernel support to EROFS, here is
> the codebase you could start with:
> https://github.com/multikernel/linux. PR is always welcome.

I think the onus is rather the other way around.  Adding a new filesystem
to Linux has a high bar to clear because it becomes a maintenance burden
to the rest of us.  Convince us that what you're doing here *can't*
be done better by modifying erofs.

Before I saw the email from Gao Xiang, I was also going to suggest that
using erofs would be a better idea than supporting your own filesystem.
Writing a new filesystem is a lot of fun.  Supporting a new filesystem
and making it production-quality is a whole lot of pain.  It's much
better if you can leverage other people's work.  That's why DAX is a
support layer for filesystems rather than its own filesystem.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ