From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Greg Kurz <groug@kaod.org>,
Keno Fischer <keno@juliacomputing.com>
Subject: [Qemu-devel] [PULL 7/7] 9p: xattr: Properly translate xattrcreate flags
Date: Thu, 7 Jun 2018 17:21:19 +0200 [thread overview]
Message-ID: <20180607152119.3447-8-groug@kaod.org> (raw)
In-Reply-To: <20180607152119.3447-1-groug@kaod.org>
From: Keno Fischer <keno@juliacomputing.com>
As with unlinkat, these flags come from the client and need to
be translated to their host values. The protocol values happen
to match linux, but that need not be true in general.
Signed-off-by: Keno Fischer <keno@juliacomputing.com>
Signed-off-by: Greg Kurz <groug@kaod.org>
---
hw/9pfs/9p.c | 17 +++++++++++++++--
hw/9pfs/9p.h | 4 ++++
2 files changed, 19 insertions(+), 2 deletions(-)
diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
index c842ec555ea1..eef289e394d4 100644
--- a/hw/9pfs/9p.c
+++ b/hw/9pfs/9p.c
@@ -3327,7 +3327,7 @@ out_nofid:
static void coroutine_fn v9fs_xattrcreate(void *opaque)
{
- int flags;
+ int flags, rflags = 0;
int32_t fid;
uint64_t size;
ssize_t err = 0;
@@ -3344,6 +3344,19 @@ static void coroutine_fn v9fs_xattrcreate(void *opaque)
}
trace_v9fs_xattrcreate(pdu->tag, pdu->id, fid, name.data, size, flags);
+ if (flags & ~(P9_XATTR_CREATE | P9_XATTR_REPLACE)) {
+ err = -EINVAL;
+ goto out_nofid;
+ }
+
+ if (flags & P9_XATTR_CREATE) {
+ rflags |= XATTR_CREATE;
+ }
+
+ if (flags & P9_XATTR_REPLACE) {
+ rflags |= XATTR_REPLACE;
+ }
+
if (size > XATTR_SIZE_MAX) {
err = -E2BIG;
goto out_nofid;
@@ -3365,7 +3378,7 @@ static void coroutine_fn v9fs_xattrcreate(void *opaque)
xattr_fidp->fs.xattr.copied_len = 0;
xattr_fidp->fs.xattr.xattrwalk_fid = false;
xattr_fidp->fs.xattr.len = size;
- xattr_fidp->fs.xattr.flags = flags;
+ xattr_fidp->fs.xattr.flags = rflags;
v9fs_string_init(&xattr_fidp->fs.xattr.name);
v9fs_string_copy(&xattr_fidp->fs.xattr.name, &name);
xattr_fidp->fs.xattr.value = g_malloc0(size);
diff --git a/hw/9pfs/9p.h b/hw/9pfs/9p.h
index bad8ee719c4b..8883761b2c1d 100644
--- a/hw/9pfs/9p.h
+++ b/hw/9pfs/9p.h
@@ -169,6 +169,10 @@ typedef struct V9fsConf
char *fsdev_id;
} V9fsConf;
+/* 9p2000.L xattr flags (matches Linux values) */
+#define P9_XATTR_CREATE 1
+#define P9_XATTR_REPLACE 2
+
typedef struct V9fsXattr
{
uint64_t copied_len;
--
2.14.4
next prev parent reply other threads:[~2018-06-07 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:21 [Qemu-devel] [PULL 0/7] 9p patches 2018-06-07 Greg Kurz
2018-06-07 15:21 ` [Qemu-devel] [PULL 1/7] 9p: proxy: Fix size passed to `connect` Greg Kurz
2018-06-07 15:21 ` [Qemu-devel] [PULL 2/7] 9p: local: Properly set errp in fstatfs error path Greg Kurz
2018-06-07 15:21 ` [Qemu-devel] [PULL 3/7] 9p: Move a couple xattr functions to 9p-util Greg Kurz
2018-06-07 15:21 ` [Qemu-devel] [PULL 4/7] 9p: xattr: Fix crashes due to free of uninitialized value Greg Kurz
2018-06-07 15:21 ` [Qemu-devel] [PULL 5/7] 9p: local: Avoid warning if FS_IOC_GETVERSION is not defined Greg Kurz
2018-06-07 15:21 ` [Qemu-devel] [PULL 6/7] 9p: Properly check/translate flags in unlinkat Greg Kurz
2018-06-07 15:21 ` Greg Kurz [this message]
2018-06-08 9:25 ` [Qemu-devel] [PULL 0/7] 9p patches 2018-06-07 Peter Maydell
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=20180607152119.3447-8-groug@kaod.org \
--to=groug@kaod.org \
--cc=keno@juliacomputing.com \
--cc=peter.maydell@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).