From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, luonengjun@huawei.com,
peter.huangpeng@huawei.com, qemu-stable@nongnu.org,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qga: Rewrite code where using readdir_r
Date: Wed, 01 Oct 2014 12:47:55 -0500 [thread overview]
Message-ID: <20141001174755.19243.37707@loki> (raw)
In-Reply-To: <1411096150-3044-1-git-send-email-zhang.zhanghailiang@huawei.com>
Quoting zhanghailiang (2014-09-18 22:09:10)
> If readdir_r fails, error_setg_errno will reference the freed
> pointer *dirpath*.
>
> Moreover, readdir_r may cause a buffer overflow, using readdir instead.
>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Thanks, applied to qga tree:
https://github.com/mdroth/qemu/commits/qga
> ---
> v2:
> - Switch readdir_r to readdir (Comment of Eric Blake)
> ---
> qga/commands-posix.c | 27 +++++++++++++++------------
> 1 file changed, 15 insertions(+), 12 deletions(-)
>
> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> index 7eed7f4..f6f3e3c 100644
> --- a/qga/commands-posix.c
> +++ b/qga/commands-posix.c
> @@ -956,7 +956,7 @@ static void build_guest_fsinfo_for_virtual_device(char const *syspath,
> {
> DIR *dir;
> char *dirpath;
> - struct dirent entry, *result;
> + struct dirent *entry;
>
> dirpath = g_strdup_printf("%s/slaves", syspath);
> dir = opendir(dirpath);
> @@ -965,22 +965,24 @@ static void build_guest_fsinfo_for_virtual_device(char const *syspath,
> g_free(dirpath);
> return;
> }
> - g_free(dirpath);
>
> for (;;) {
> - if (readdir_r(dir, &entry, &result) != 0) {
> - error_setg_errno(errp, errno, "readdir_r(\"%s\")", dirpath);
> - break;
> - }
> - if (!result) {
> + errno = 0;
> + entry = readdir(dir);
> + if (entry == NULL) {
> + if (errno) {
> + error_setg_errno(errp, errno, "readdir(\"%s\")", dirpath);
> + }
> break;
> }
>
> - if (entry.d_type == DT_LNK) {
> - g_debug(" slave device '%s'", entry.d_name);
> - dirpath = g_strdup_printf("%s/slaves/%s", syspath, entry.d_name);
> - build_guest_fsinfo_for_device(dirpath, fs, errp);
> - g_free(dirpath);
> + if (entry->d_type == DT_LNK) {
> + char *path;
> +
> + g_debug(" slave device '%s'", entry->d_name);
> + path = g_strdup_printf("%s/slaves/%s", syspath, entry->d_name);
> + build_guest_fsinfo_for_device(path, fs, errp);
> + g_free(path);
>
> if (*errp) {
> break;
> @@ -988,6 +990,7 @@ static void build_guest_fsinfo_for_virtual_device(char const *syspath,
> }
> }
>
> + g_free(dirpath);
> closedir(dir);
> }
>
> --
> 1.7.12.4
prev parent reply other threads:[~2014-10-01 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 3:09 [Qemu-devel] [PATCH v2] qga: Rewrite code where using readdir_r zhanghailiang
2014-09-26 8:32 ` zhanghailiang
2014-09-26 15:40 ` Paolo Bonzini
2014-09-28 6:06 ` zhanghailiang
2014-09-26 15:45 ` Eric Blake
2014-10-01 17:47 ` Michael Roth [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=20141001174755.19243.37707@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=luonengjun@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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 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).