From: Vivek Goyal <vgoyal@redhat.com> To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> Cc: dinechin@redhat.com, virtio-fs@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com Subject: Re: [PATCH v3 2/5] tools/virtiofsd: xattr name mappings: Map client xattr names Date: Thu, 22 Oct 2020 11:28:53 -0400 [thread overview] Message-ID: <20201022152853.GC512900@redhat.com> (raw) In-Reply-To: <20201014180209.49299-3-dgilbert@redhat.com> On Wed, Oct 14, 2020 at 07:02:06PM +0100, Dr. David Alan Gilbert (git) wrote: > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com> > > Map xattr names originating at the client; from get/set/remove xattr. > > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> > --- > tools/virtiofsd/passthrough_ll.c | 101 ++++++++++++++++++++++++++++++- > 1 file changed, 98 insertions(+), 3 deletions(-) > > diff --git a/tools/virtiofsd/passthrough_ll.c b/tools/virtiofsd/passthrough_ll.c > index f5a33014f9..57ebe17ed6 100644 > --- a/tools/virtiofsd/passthrough_ll.c > +++ b/tools/virtiofsd/passthrough_ll.c > @@ -2183,20 +2183,80 @@ static XattrMapEntry *parse_xattrmap(struct lo_data *lo) > return res; > } > > -static void lo_getxattr(fuse_req_t req, fuse_ino_t ino, const char *name, > +/* > + * For use with getxattr/setxattr/removexattr, where the client > + * gives us a name and we may need to choose a different one. > + * Allocates a buffer for the result placing it in *out_name. > + * If there's no change then *out_name is not set. > + * Returns 0 on success > + * Can return -EPERM to indicate we block a given attribute > + * (in which case out_name is not allocated) > + * Can return -ENOMEM to indicate out_name couldn't be allocated. > + */ > +static int xattr_map_client(const struct lo_data *lo, const char *client_name, > + char **out_name) > +{ > + const XattrMapEntry *cur_entry; > + > + for (cur_entry = lo->xattr_map_list; ; cur_entry++) { > + if ((cur_entry->flags & XATTR_MAP_FLAG_CLIENT) && > + (strstart(client_name, cur_entry->key, NULL))) { > + if (cur_entry->flags & XATTR_MAP_FLAG_END_BAD) { > + return -EPERM; > + } > + if (cur_entry->flags & XATTR_MAP_FLAG_END_OK) { > + /* Unmodified name */ > + return 0; > + } > + if (cur_entry->flags & XATTR_MAP_FLAG_PREFIX) { I am wondering why do have "END" substring in BAD and OK flags while we don't have one in PREFIX flag. IOW, why not simply call these flags as XATTR_MAP_FLAG_OK and XATTR_MAP_FLAG_BAD respectively. > + *out_name = g_try_malloc(strlen(client_name) + > + strlen(cur_entry->prepend) + 1); Should we check for cur_entry->prepend to be NULL before we try to allocate out_name. One could say. "prefix:client:trusted.::". In that case we are not supposed to prefix anything? > + if (!*out_name) { > + return -ENOMEM; > + } > + sprintf(*out_name, "%s%s", cur_entry->prepend, client_name); > + return 0; > + } > + } > + } > + > + /* Shouldn't get here - rules should have an END_* */ > + abort(); > +} Thanks Vivek
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com> To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> Cc: dinechin@redhat.com, virtio-fs@redhat.com, qemu-devel@nongnu.org Subject: Re: [Virtio-fs] [PATCH v3 2/5] tools/virtiofsd: xattr name mappings: Map client xattr names Date: Thu, 22 Oct 2020 11:28:53 -0400 [thread overview] Message-ID: <20201022152853.GC512900@redhat.com> (raw) In-Reply-To: <20201014180209.49299-3-dgilbert@redhat.com> On Wed, Oct 14, 2020 at 07:02:06PM +0100, Dr. David Alan Gilbert (git) wrote: > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com> > > Map xattr names originating at the client; from get/set/remove xattr. > > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> > --- > tools/virtiofsd/passthrough_ll.c | 101 ++++++++++++++++++++++++++++++- > 1 file changed, 98 insertions(+), 3 deletions(-) > > diff --git a/tools/virtiofsd/passthrough_ll.c b/tools/virtiofsd/passthrough_ll.c > index f5a33014f9..57ebe17ed6 100644 > --- a/tools/virtiofsd/passthrough_ll.c > +++ b/tools/virtiofsd/passthrough_ll.c > @@ -2183,20 +2183,80 @@ static XattrMapEntry *parse_xattrmap(struct lo_data *lo) > return res; > } > > -static void lo_getxattr(fuse_req_t req, fuse_ino_t ino, const char *name, > +/* > + * For use with getxattr/setxattr/removexattr, where the client > + * gives us a name and we may need to choose a different one. > + * Allocates a buffer for the result placing it in *out_name. > + * If there's no change then *out_name is not set. > + * Returns 0 on success > + * Can return -EPERM to indicate we block a given attribute > + * (in which case out_name is not allocated) > + * Can return -ENOMEM to indicate out_name couldn't be allocated. > + */ > +static int xattr_map_client(const struct lo_data *lo, const char *client_name, > + char **out_name) > +{ > + const XattrMapEntry *cur_entry; > + > + for (cur_entry = lo->xattr_map_list; ; cur_entry++) { > + if ((cur_entry->flags & XATTR_MAP_FLAG_CLIENT) && > + (strstart(client_name, cur_entry->key, NULL))) { > + if (cur_entry->flags & XATTR_MAP_FLAG_END_BAD) { > + return -EPERM; > + } > + if (cur_entry->flags & XATTR_MAP_FLAG_END_OK) { > + /* Unmodified name */ > + return 0; > + } > + if (cur_entry->flags & XATTR_MAP_FLAG_PREFIX) { I am wondering why do have "END" substring in BAD and OK flags while we don't have one in PREFIX flag. IOW, why not simply call these flags as XATTR_MAP_FLAG_OK and XATTR_MAP_FLAG_BAD respectively. > + *out_name = g_try_malloc(strlen(client_name) + > + strlen(cur_entry->prepend) + 1); Should we check for cur_entry->prepend to be NULL before we try to allocate out_name. One could say. "prefix:client:trusted.::". In that case we are not supposed to prefix anything? > + if (!*out_name) { > + return -ENOMEM; > + } > + sprintf(*out_name, "%s%s", cur_entry->prepend, client_name); > + return 0; > + } > + } > + } > + > + /* Shouldn't get here - rules should have an END_* */ > + abort(); > +} Thanks Vivek
next prev parent reply other threads:[~2020-10-22 15:30 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-14 18:02 [PATCH v3 0/5] virtiofsd xattr name mappings Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " 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 [this message] 2020-10-22 15:28 ` 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=20201022152853.GC512900@redhat.com \ --to=vgoyal@redhat.com \ --cc=dgilbert@redhat.com \ --cc=dinechin@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=stefanha@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: linkBe 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.