All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, stefanha@redhat.com, vgoyal@redhat.com,
	dinechin@redhat.com, virtio-fs@redhat.com
Subject: [PATCH v3 0/5] virtiofsd xattr name mappings
Date: Wed, 14 Oct 2020 19:02:04 +0100	[thread overview]
Message-ID: <20201014180209.49299-1-dgilbert@redhat.com> (raw)

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

This is a 3rd cut of an xattr name mapping option for virtiofsd.
It allows the user of virtiofsd to define a fairly flexible mapping
from the view of the xattr names the host fs has and the ones that the
guest sees.

  The hope is this allows things like:
    a) Different selinux attributes on host/guest
    b) separation of trusted. attributes that clash on overlayfs
    c) support for privileged xattr's in guests running with an
       unprivileged virtiofsd.

There's no apparent standard for this kind of mapping, so I made
it flexible by specifying a mapping rule in the option.

Prefix's can be added (selectively or globally), xattr's can be
dropped in either direction or passed through.

The major change for v3 is the addition of a 'map' simple syntax
that should cover a lot of the simple cases without people needing
to use the more complex rule syntax.  There's also some cleanups
basedon reviews by Christophe.

Dave


Dr. David Alan Gilbert (5):
  tools/virtiofsd: xattr name mappings: Add option
  tools/virtiofsd: xattr name mappings: Map client xattr names
  tools/virtiofsd: xattr name mappings: Map server xattr names
  tools/virtiofsd: xattr name mapping examples
  tools/virtiofsd: xattr name mappings: Simple 'map'

 docs/tools/virtiofsd.rst         | 122 ++++++++
 tools/virtiofsd/passthrough_ll.c | 476 ++++++++++++++++++++++++++++++-
 2 files changed, 595 insertions(+), 3 deletions(-)

-- 
2.28.0



WARNING: multiple messages have this Message-ID (diff)
From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, stefanha@redhat.com, vgoyal@redhat.com,
	dinechin@redhat.com, virtio-fs@redhat.com
Subject: [Virtio-fs] [PATCH v3 0/5] virtiofsd xattr name mappings
Date: Wed, 14 Oct 2020 19:02:04 +0100	[thread overview]
Message-ID: <20201014180209.49299-1-dgilbert@redhat.com> (raw)

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

This is a 3rd cut of an xattr name mapping option for virtiofsd.
It allows the user of virtiofsd to define a fairly flexible mapping
from the view of the xattr names the host fs has and the ones that the
guest sees.

  The hope is this allows things like:
    a) Different selinux attributes on host/guest
    b) separation of trusted. attributes that clash on overlayfs
    c) support for privileged xattr's in guests running with an
       unprivileged virtiofsd.

There's no apparent standard for this kind of mapping, so I made
it flexible by specifying a mapping rule in the option.

Prefix's can be added (selectively or globally), xattr's can be
dropped in either direction or passed through.

The major change for v3 is the addition of a 'map' simple syntax
that should cover a lot of the simple cases without people needing
to use the more complex rule syntax.  There's also some cleanups
basedon reviews by Christophe.

Dave


Dr. David Alan Gilbert (5):
  tools/virtiofsd: xattr name mappings: Add option
  tools/virtiofsd: xattr name mappings: Map client xattr names
  tools/virtiofsd: xattr name mappings: Map server xattr names
  tools/virtiofsd: xattr name mapping examples
  tools/virtiofsd: xattr name mappings: Simple 'map'

 docs/tools/virtiofsd.rst         | 122 ++++++++
 tools/virtiofsd/passthrough_ll.c | 476 ++++++++++++++++++++++++++++++-
 2 files changed, 595 insertions(+), 3 deletions(-)

-- 
2.28.0


             reply	other threads:[~2020-10-14 18:03 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 18:02 Dr. David Alan Gilbert (git) [this message]
2020-10-14 18:02 ` [Virtio-fs] [PATCH v3 0/5] virtiofsd xattr name mappings Dr. David Alan Gilbert (git)
2020-10-14 18:02 ` [PATCH v3 1/5] tools/virtiofsd: xattr name mappings: Add option Dr. David Alan Gilbert (git)
2020-10-14 18:02   ` [Virtio-fs] " Dr. David Alan Gilbert (git)
2020-10-20  9:07   ` Stefan Hajnoczi
2020-10-20  9:07     ` [Virtio-fs] " Stefan Hajnoczi
2020-10-21 17:13     ` Dr. David Alan Gilbert
2020-10-21 17:13       ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-20 14:04   ` Vivek Goyal
2020-10-20 14:04     ` [Virtio-fs] " Vivek Goyal
2020-10-22 14:52   ` Vivek Goyal
2020-10-22 14:52     ` [Virtio-fs] " Vivek Goyal
2020-10-23 15:46     ` Dr. David Alan Gilbert
2020-10-23 15:46       ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-14 18:02 ` [PATCH v3 2/5] tools/virtiofsd: xattr name mappings: Map client xattr names Dr. David Alan Gilbert (git)
2020-10-14 18:02   ` [Virtio-fs] " Dr. David Alan Gilbert (git)
2020-10-20  9:16   ` Stefan Hajnoczi
2020-10-20  9:16     ` [Virtio-fs] " Stefan Hajnoczi
2020-10-22 15:28   ` Vivek Goyal
2020-10-22 15:28     ` [Virtio-fs] " Vivek Goyal
2020-10-23 15:04     ` Dr. David Alan Gilbert
2020-10-23 15:04       ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-14 18:02 ` [PATCH v3 3/5] tools/virtiofsd: xattr name mappings: Map server " Dr. David Alan Gilbert (git)
2020-10-14 18:02   ` [Virtio-fs] " Dr. David Alan Gilbert (git)
2020-10-15 23:57   ` [Virtio-fs] Puzzle about rootflags, restorecon "operation not supported" Harry G. Coin
2020-10-20  9:54     ` Stefan Hajnoczi
2020-10-20 12:57       ` Miklos Szeredi
2020-10-20 14:55         ` Harry G. Coin
2020-10-20  9:52   ` [PATCH v3 3/5] tools/virtiofsd: xattr name mappings: Map server xattr names Stefan Hajnoczi
2020-10-20  9:52     ` [Virtio-fs] " Stefan Hajnoczi
2020-10-22 16:16   ` Vivek Goyal
2020-10-22 16:16     ` [Virtio-fs] " Vivek Goyal
2020-10-23 14:49     ` Dr. David Alan Gilbert
2020-10-23 14:49       ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-14 18:02 ` [PATCH v3 4/5] tools/virtiofsd: xattr name mapping examples Dr. David Alan Gilbert (git)
2020-10-14 18:02   ` [Virtio-fs] " Dr. David Alan Gilbert (git)
2020-10-20  9:56   ` Stefan Hajnoczi
2020-10-20  9:56     ` [Virtio-fs] " Stefan Hajnoczi
2020-10-20 14:40   ` Vivek Goyal
2020-10-20 14:40     ` [Virtio-fs] " Vivek Goyal
2020-10-20 15:34     ` Dr. David Alan Gilbert
2020-10-20 15:34       ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-20 17:56       ` Vivek Goyal
2020-10-20 17:56         ` [Virtio-fs] " Vivek Goyal
2020-10-20 19:02         ` Dr. David Alan Gilbert
2020-10-20 19:02           ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-21 13:44           ` Vivek Goyal
2020-10-21 13:44             ` [Virtio-fs] " Vivek Goyal
2020-10-21 17:39             ` Dr. David Alan Gilbert
2020-10-21 17:39               ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-14 18:02 ` [PATCH v3 5/5] tools/virtiofsd: xattr name mappings: Simple 'map' Dr. David Alan Gilbert (git)
2020-10-14 18:02   ` [Virtio-fs] " Dr. David Alan Gilbert (git)
2020-10-20 10:09   ` Stefan Hajnoczi
2020-10-20 10:09     ` [Virtio-fs] " Stefan Hajnoczi
2020-10-20 11:35     ` Dr. David Alan Gilbert
2020-10-20 11:35       ` [Virtio-fs] " Dr. David Alan Gilbert
2020-10-22 13:42   ` Vivek Goyal
2020-10-22 13:42     ` [Virtio-fs] " Vivek Goyal
2020-10-23 13:05     ` Dr. David Alan Gilbert
2020-10-23 13:05       ` [Virtio-fs] " Dr. David Alan Gilbert

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=20201014180209.49299-1-dgilbert@redhat.com \
    --to=dgilbert@redhat.com \
    --cc=dinechin@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=virtio-fs@redhat.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 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.