mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ali Ahmet Memis <ali@iusegentoo.com>
To: jack@suse.cz
Cc: willy@infradead.org, viro@zeniv.linux.org.uk, brauner@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add myself as UFS filesystem maintainer
Date: Mon,  3 Aug 2026 09:44:10 +0000	[thread overview]
Message-ID: <20260803094412.8059-1-ali@iusegentoo.com> (raw)
In-Reply-To: <opm7uuadw7ctvvo6uln22nb6id3pepcs4nohunq7tzeaciq3kc@kigwxsd3pcbo>

On Mon, Aug 03, 2026 at 10:57:14AM +0200, Jan Kara wrote:
> I'm a bit curious: Are you using UFS driver in Linux? Or do you know of
> anybody using it?

Yes. I run FreeBSD on a second machine that I keep as a small server, and
its disks are UFS2. I mount those from my Linux box with the in-tree ufs
driver to read data off them, which on Linux is read-only for UFS2. So the
driver is not theoretical for me, it is how I reach my own data.

More generally that is what the driver is for: reading FreeBSD, NetBSD,
OpenBSD and Solaris disks from Linux. Anyone dual booting a BSD, migrating
data off one, or doing recovery or forensics on a BSD or Solaris volume
ends up here. It is a small user base but not an empty one, and it is the
only in-tree way to do it.

That is also why the mount path bugs bother me. The images I feed it are
real BSD volumes, sometimes left unclean after a crash, so an unusual but
legitimate on-disk layout should not panic the kernel. The fixes I have
been sending are all in that parse and mount path.

Thanks,
Ali

  reply	other threads:[~2026-08-03  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  2:50 Ali Ahmet Memis
2026-08-01  4:23 ` Matthew Wilcox
2026-08-01  7:30   ` Ali Ahmet Memis
2026-08-03  8:57     ` Jan Kara
2026-08-03  9:44       ` Ali Ahmet Memis [this message]
2026-08-03 10:00         ` Jan Kara

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=20260803094412.8059-1-ali@iusegentoo.com \
    --to=ali@iusegentoo.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    /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®