From: Greg Kurz <groug@kaod.org>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, "Léo Gaspard" <leo@gaspard.io>
Subject: Re: [Qemu-devel] [PATCH 3/5] 9pfs: local: simplify file opening
Date: Tue, 9 May 2017 11:23:05 +0200 [thread overview]
Message-ID: <20170509112305.439c4d85@bahia> (raw)
In-Reply-To: <3c8abd95-b490-1b71-b467-4f00d6ce121d@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
On Fri, 5 May 2017 12:01:55 -0500
Eric Blake <eblake@redhat.com> wrote:
> On 05/05/2017 09:37 AM, Greg Kurz wrote:
> > All paths in the virtfs directory now start with "./" (except the virtfs
> > root itself which is exactly ".").
> >
> > We hence don't need to skip leading '/' characters anymore, nor to handle
> > the empty path case. Also, since virtfs will only ever be supported on
> > linux+glibc hosts, we can use strchrnul() and come up with a much simplier
> > code to walk through the path elements. And we don't need to dup() the
> > passed directory fd.
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > hw/9pfs/9p-local.c | 5 -----
> > hw/9pfs/9p-util.c | 26 ++++++++++----------------
> > 2 files changed, 10 insertions(+), 21 deletions(-)
> >
> > diff --git a/hw/9pfs/9p-local.c b/hw/9pfs/9p-local.c
> > index 92262f3c3e37..bb6e296df317 100644
> > --- a/hw/9pfs/9p-local.c
> > +++ b/hw/9pfs/9p-local.c
> > @@ -54,11 +54,6 @@ int local_open_nofollow(FsContext *fs_ctx, const char *path, int flags,
> > {
> > LocalData *data = fs_ctx->private;
> >
> > - /* All paths are relative to the path data->mountfd points to */
> > - while (*path == '/') {
> > - path++;
> > - }
>
> Is it worth adding any assert()s in place of the deleted code?
>
The assert() added by this patch ensures that we never pass an empty
string to relative_openat_nofollow(), which isn't related to this
hunk of deleted code... so I'm not sure I understand the question :-\
> Otherwise looks okay.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-05-09 9:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 14:36 [Qemu-devel] [PATCH 0/5] 9pfs: local: fix metadata of mapped-file security mode Greg Kurz
2017-05-05 14:37 ` [Qemu-devel] [PATCH 1/5] 9pfs: check return value of v9fs_co_name_to_path() Greg Kurz
2017-05-05 16:55 ` Eric Blake
2017-05-05 17:30 ` Greg Kurz
2017-05-05 14:37 ` [Qemu-devel] [PATCH 2/5] 9pfs: local: resolve special directories in paths Greg Kurz
2017-05-05 16:59 ` Eric Blake
2017-05-09 9:12 ` Greg Kurz
2017-05-18 8:41 ` Greg Kurz
2017-05-18 14:19 ` Eric Blake
2017-05-05 14:37 ` [Qemu-devel] [PATCH 3/5] 9pfs: local: simplify file opening Greg Kurz
2017-05-05 17:01 ` Eric Blake
2017-05-09 9:23 ` Greg Kurz [this message]
2017-05-18 8:42 ` Greg Kurz
2017-05-18 14:23 ` Eric Blake
2017-05-18 15:51 ` Greg Kurz
2017-05-05 14:37 ` [Qemu-devel] [PATCH 4/5] 9pfs: local: metadata file for the VirtFS root Greg Kurz
2017-05-05 17:11 ` Eric Blake
2017-05-09 9:31 ` Greg Kurz
2017-05-05 14:37 ` [Qemu-devel] [PATCH 5/5] 9pfs: local: forbid client access to metadata Greg Kurz
2017-05-05 17:13 ` Eric Blake
2017-05-09 9:39 ` Greg Kurz
2017-05-05 15:25 ` [Qemu-devel] [PATCH 0/5] 9pfs: local: fix metadata of mapped-file security mode no-reply
2017-05-08 15:33 ` Leo Gaspard
2017-05-09 9:42 ` Greg Kurz
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=20170509112305.439c4d85@bahia \
--to=groug@kaod.org \
--cc=eblake@redhat.com \
--cc=leo@gaspard.io \
--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 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.