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: Fri, 05 Sep 2025 13:19:39 +0200 [thread overview]
Message-ID: <2537259.JahZeRKPxa@silver> (raw)
In-Reply-To: <aJOWhHB2p-fbueAm@nuc>
On Wednesday, August 6, 2025 7:53:08 PM CEST Mark Johnston wrote:
> 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." on ZFS, so the prefix is
> trimmed off. FreeBSD's extattr system calls sport an extra
> "namespace" identifier, and attributes created by the 9pfs backend
> live in the universal user namespace, so this seems innocent enough.
>
> The 9pfs tests were verified to pass on the UFS, ZFS and tmpfs
> filesystems.
>
> Signed-off-by: Mark Johnston <markj@FreeBSD.org>
> ---
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
/Christian
prev parent reply other threads:[~2025-09-05 11:21 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
2025-09-01 10:40 ` Greg Kurz
2025-09-05 11:19 ` Christian Schoenebeck [this message]
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=2537259.JahZeRKPxa@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 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).