qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org, "Mark Johnston" <markj@freebsd.org>,
	"Greg Kurz" <groug@kaod.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] 9pfs: Add FreeBSD support
Date: Tue, 29 Jul 2025 17:13:03 +0100	[thread overview]
Message-ID: <aIjzD76zstbZcjtX@redhat.com> (raw)
In-Reply-To: <1989897.fkXqvmx5VE@silver>

On Tue, Jul 29, 2025 at 06:09:35PM +0200, Christian Schoenebeck wrote:
> On Wednesday, July 23, 2025 5:55:58 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>
> 
> Hi Mark,
> 
> first off, the problem is I currently don't have a FreeBSD host to test and
> won't have the time in near future neither.
> 
> So what was your general intention regarding this patch, fire and forget, or
> would you be around for issues/patches regarding 9pfs FreeBSD support?
> 
> > ---
> >  fsdev/file-op-9p.h        |   6 +-
> >  fsdev/meson.build         |   2 +-
> >  hw/9pfs/9p-synth.c        |   2 +-
> >  hw/9pfs/9p-util-freebsd.c | 124 ++++++++++++++++++++++++++++++++++++++
> >  hw/9pfs/9p-util.h         |  19 ++++--
> >  hw/9pfs/9p.c              |  16 ++++-
> >  hw/9pfs/meson.build       |   2 +
> >  include/qemu/xattr.h      |   6 +-
> >  meson.build               |   8 +--
> >  9 files changed, 170 insertions(+), 15 deletions(-)
> >  create mode 100644 hw/9pfs/9p-util-freebsd.c

> > diff --git a/hw/9pfs/9p-util-freebsd.c b/hw/9pfs/9p-util-freebsd.c
> > new file mode 100644
> > index 0000000000..e649f79d4b
> > --- /dev/null
> > +++ b/hw/9pfs/9p-util-freebsd.c
> > @@ -0,0 +1,124 @@
> > +/*
> > + * 9p utilities (FreeBSD Implementation)
> > + *
> > + * This work is licensed under the terms of the GNU GPL, version 2 or later.
> > + * See the COPYING file in the top-level directory.
> > + */
> 
> I think for new source files in QEMU the policy is to use
> SPDX-License-Identifier: ... now?

Yes, checkpatch.pl should complain both about the missing SPDX tag
and about this license blurb which would be redundant if SPDX were
present.


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-07-29 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 15:55 [PATCH] 9pfs: Add FreeBSD support Mark Johnston
2025-07-29 16:09 ` Christian Schoenebeck
2025-07-29 16:13   ` Daniel P. Berrangé [this message]
2025-07-30 14:32   ` Mark Johnston
2025-07-30 14:35     ` Daniel P. Berrangé
2025-08-05 11:49     ` Christian Schoenebeck
2025-08-06 17:37       ` Mark Johnston

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=aIjzD76zstbZcjtX@redhat.com \
    --to=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 \
    --cc=qemu_oss@crudebyte.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).