From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Mark Johnston <markj@freebsd.org>
Cc: "Greg Kurz" <groug@kaod.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2] 9pfs: Add FreeBSD support
Date: Mon, 01 Sep 2025 12:31:32 +0200 [thread overview]
Message-ID: <2671619.RrsIbz4Ki0@silver> (raw)
In-Reply-To: <aK8WUWSIV6Bz526v@nuc>
On Wednesday, August 27, 2025 4:29:37 PM CEST Mark Johnston wrote:
> On Tue, Aug 26, 2025 at 02:34:45PM +0200, Christian Schoenebeck wrote:
[...]
> I folded your suggestion in with a couple of minor tweaks:
>
> commit 61de78986912b03f08354a177caf603857b531b5
> Author: Mark Johnston <markj@FreeBSD.org>
> Date: Wed Jul 16 20:32:05 2025 +0000
>
> 9pfs: Add FreeBSD support
>
> This is largely derived from existing Darwin support. FreeBSD
> apparently has better support for *at() system calls so doesn't require
> workarounds for a missing mknodat(). The implementation has a couple of
> warts however:
> - The extattr(2) system calls don't support anything akin to
> XATTR_CREATE or XATTR_REPLACE, so a racy workaround is implemented.
> - Attribute names cannot begin with "user." or "system." on ZFS.
> However FreeBSD's extattr(2) system calls support two dedicated
> namespaces for these two. So "user." or "system." prefixes are
> trimmed off from attribute names and instead EXTATTR_NAMESPACE_USER or
> EXTATTR_NAMESPACE_SYSTEM are picked and passed to extattr system calls
> accordingly.
>
> The 9pfs tests were verified to pass on the UFS, ZFS and tmpfs
> filesystems.
>
> Signed-off-by: Mark Johnston <markj@FreeBSD.org>
LGTM, thanks!
/Christian
next prev parent reply other threads:[~2025-09-01 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 17:53 [PATCH v2] 9pfs: Add FreeBSD support Mark Johnston
2025-08-21 11:24 ` Christian Schoenebeck
2025-08-25 12:53 ` Mark Johnston
2025-08-26 12:34 ` Christian Schoenebeck
2025-08-27 14:29 ` Mark Johnston
2025-09-01 10:31 ` Christian Schoenebeck [this message]
2025-09-01 10:40 ` Greg Kurz
2025-09-05 11:19 ` Christian Schoenebeck
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=2671619.RrsIbz4Ki0@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.com \
--cc=groug@kaod.org \
--cc=marcandre.lureau@redhat.com \
--cc=markj@freebsd.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.