From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] 9p-local.c: always return -1 on error in local_unlinkat_common
Date: Tue, 7 Jan 2020 16:21:38 -0300 [thread overview]
Message-ID: <254ea08e-ef26-a61d-6144-404f035c21e8@gmail.com> (raw)
In-Reply-To: <20200107174726.5640a059@bahia.lan>
On 1/7/20 1:47 PM, Greg Kurz wrote:
> I've changed "9p-local.c:" to "9p: local:" which is the usual prefix used for
> fsdev backend specific changes.
Good to know. Thanks for fixing it up.
>
> On Tue, 7 Jan 2020 11:47:18 -0300
> Daniel Henrique Barboza <danielhb413@gmail.com> wrote:
>
>> local_unlinkat_common() is supposed to always return -1 on error.
>> This is being done by jumps to the 'err_out' label, which is
>> a 'return ret' call, and 'ret' is initialized with -1.
>>
>> Unfortunately there is a condition in which the function will
>> return 0 on error: in a case where flags == AT_REMOVEDIR, 'ret'
>> will be 0 when reaching
>>
>> map_dirfd = openat_dir(...)
>>
>> And, if map_dirfd == -1 and errno != ENOENT, the existing 'err_out'
>> jump will execute 'return ret', when ret is still set to zero
>> at that point.
>>
>> This patch fixes it by changing all 'err_out' labels by
>> 'return -1' calls, ensuring that the function will always
>> return -1 on error conditions. 'ret' can be left unintialized
>> since it's now being used just to store the result of 'unlinkat'
>> calls.
>>
>> CC: Greg Kurz <groug@kaod.org>
>> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
>> ---
>
> Applied to 9p-next.
>
> Thanks Daniel and feliz ano novo :)
Bonne année!
>
>> hw/9pfs/9p-local.c | 14 ++++++--------
>> 1 file changed, 6 insertions(+), 8 deletions(-)
>>
>> diff --git a/hw/9pfs/9p-local.c b/hw/9pfs/9p-local.c
>> index ca641390fb..de61aca216 100644
>> --- a/hw/9pfs/9p-local.c
>> +++ b/hw/9pfs/9p-local.c
>> @@ -1076,7 +1076,7 @@ out:
>> static int local_unlinkat_common(FsContext *ctx, int dirfd, const char *name,
>> int flags)
>> {
>> - int ret = -1;
>> + int ret;
>>
>> if (ctx->export_flags & V9FS_SM_MAPPED_FILE) {
>> int map_dirfd;
>> @@ -1094,12 +1094,12 @@ static int local_unlinkat_common(FsContext *ctx, int dirfd, const char *name,
>>
>> fd = openat_dir(dirfd, name);
>> if (fd == -1) {
>> - goto err_out;
>> + return -1;
>> }
>> ret = unlinkat(fd, VIRTFS_META_DIR, AT_REMOVEDIR);
>> close_preserve_errno(fd);
>> if (ret < 0 && errno != ENOENT) {
>> - goto err_out;
>> + return -1;
>> }
>> }
>> map_dirfd = openat_dir(dirfd, VIRTFS_META_DIR);
>> @@ -1107,16 +1107,14 @@ static int local_unlinkat_common(FsContext *ctx, int dirfd, const char *name,
>> ret = unlinkat(map_dirfd, name, 0);
>> close_preserve_errno(map_dirfd);
>> if (ret < 0 && errno != ENOENT) {
>> - goto err_out;
>> + return -1;
>> }
>> } else if (errno != ENOENT) {
>> - goto err_out;
>> + return -1;
>> }
>> }
>>
>> - ret = unlinkat(dirfd, name, flags);
>> -err_out:
>> - return ret;
>> + return unlinkat(dirfd, name, flags);
>> }
>>
>> static int local_remove(FsContext *ctx, const char *path)
>
prev parent reply other threads:[~2020-01-07 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 14:47 [PATCH 1/1] 9p-local.c: always return -1 on error in local_unlinkat_common Daniel Henrique Barboza
2020-01-07 16:47 ` Greg Kurz
2020-01-07 19:21 ` Daniel Henrique Barboza [this message]
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=254ea08e-ef26-a61d-6144-404f035c21e8@gmail.com \
--to=danielhb413@gmail.com \
--cc=groug@kaod.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).