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 1/5] 9pfs: check return value of v9fs_co_name_to_path()
Date: Fri, 5 May 2017 19:30:46 +0200 [thread overview]
Message-ID: <20170505193046.6c9bf2c1@bahia> (raw)
In-Reply-To: <e1843524-9ec7-2aea-4138-f3ce246f0929@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
On Fri, 5 May 2017 11:55:43 -0500
Eric Blake <eblake@redhat.com> wrote:
> On 05/05/2017 09:37 AM, Greg Kurz wrote:
> > These v9fs_co_name_to_path() call sites have always been around. I guess
> > no care was taken to check the return value because the name_to_path
> > operation could never fail at the time. This is no longer true: the
> > handle and synth backends can already fail this operation, and so will the
> > local backend soon.
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > hw/9pfs/9p.c | 36 +++++++++++++++++++++++++-----------
> > 1 file changed, 25 insertions(+), 11 deletions(-)
> >
>
> > @@ -2588,8 +2591,11 @@ static int coroutine_fn v9fs_complete_rename(V9fsPDU *pdu, V9fsFidState *fidp,
> > new_name = g_malloc0(end - old_name + name->size + 1);
> > strncat(new_name, old_name, end - old_name);
> > strncat(new_name + (end - old_name), name->data, name->size);
>
> Ad long as you're here, you could replace this strncat mess with the
> shorter:
>
> new_name = g_strdup_printf("%.*s%.*s", end - old_name, old_name,
> name->size, name->data);
>
> (or with further simplifications if you have NUL-terminated data). But
> that can be a separate cleanup.
>
Yes you're right, this definitely looks better than the strncat() logic.
I guess I'll do this in a separate patch.
Thanks for the suggestion.
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-05-05 17:30 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 [this message]
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
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=20170505193046.6c9bf2c1@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 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).