From: Vivek Goyal <vgoyal@redhat.com>
To: virtio-fs-list <virtio-fs@redhat.com>
Subject: [Virtio-fs] [PATCH] virtiofsd: Open fd O_RDONLY in setxattr/removexattr
Date: Wed, 8 Jan 2020 15:24:22 -0500 [thread overview]
Message-ID: <20200108202422.GF1995@redhat.com> (raw)
Do not open fd O_RDWR as it will fail for directories with EISDIR. This
code can be called both for regular files as well as directories.
I noticed this when I tried "setfattr -n user.foo -v test <dir>" inside
the guest and got EISDIR.
To write xattr, we don't have to open fd with write permissions. Looks
like kernel will do permission checks on inode.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
contrib/virtiofsd/passthrough_ll.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: qemu/contrib/virtiofsd/passthrough_ll.c
===================================================================
--- qemu.orig/contrib/virtiofsd/passthrough_ll.c 2020-01-08 15:01:03.821980889 -0500
+++ qemu/contrib/virtiofsd/passthrough_ll.c 2020-01-08 15:05:15.209384352 -0500
@@ -2424,7 +2424,7 @@ static void lo_setxattr(fuse_req_t req,
}
sprintf(procname, "%i", inode->fd);
- fd = openat(lo->proc_self_fd, procname, O_RDWR);
+ fd = openat(lo->proc_self_fd, procname, O_RDONLY);
if (fd < 0) {
saverr = errno;
goto out;
@@ -2473,7 +2473,7 @@ static void lo_removexattr(fuse_req_t re
}
sprintf(procname, "%i", inode->fd);
- fd = openat(lo->proc_self_fd, procname, O_RDWR);
+ fd = openat(lo->proc_self_fd, procname, O_RDONLY);
if (fd < 0) {
saverr = errno;
goto out;
next reply other threads:[~2020-01-08 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 20:24 Vivek Goyal [this message]
2020-01-09 2:23 ` [Virtio-fs] [PATCH] virtiofsd: Open fd O_RDONLY in setxattr/removexattr Eryu Guan
2020-01-09 9:27 ` misono.tomohiro
2020-01-09 17:56 ` Vivek Goyal
2020-01-09 19:10 ` Vivek Goyal
2020-01-10 0:50 ` misono.tomohiro
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=20200108202422.GF1995@redhat.com \
--to=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.