qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: kwolf@redhat.com, alex@alex.org.uk, mst@redhat.com,
	luonengjun@huawei.com, peter.huangpeng@huawei.com,
	qemu-devel@nongnu.org, stefanha@redhat.com, pbonzini@redhat.com,
	lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/4] monitor: fix access freed memory
Date: Mon, 04 Aug 2014 10:01:09 +0100	[thread overview]
Message-ID: <87fvhcvdam.fsf@linaro.org> (raw)
In-Reply-To: <1407140744-11948-3-git-send-email-zhang.zhanghailiang@huawei.com>


zhanghailiang writes:

> The function monitor_fdset_dup_fd_find_remove() references member of 'mon_fdset'
> which may be freed in function monitor_fdset_cleanup()
>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> ---
>  monitor.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/monitor.c b/monitor.c
> index 5bc70a6..41e46a6 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -2532,8 +2532,10 @@ static int monitor_fdset_dup_fd_find_remove(int dup_fd, bool remove)
>  {
>      MonFdset *mon_fdset;
>      MonFdsetFd *mon_fdset_fd_dup;
> +    int64_t id = -1;
>  
>      QLIST_FOREACH(mon_fdset, &mon_fdsets, next) {
> +        id = mon_fdset->id;
>          QLIST_FOREACH(mon_fdset_fd_dup, &mon_fdset->dup_fds, next) {
>              if (mon_fdset_fd_dup->fd == dup_fd) {
>                  if (remove) {
> @@ -2542,7 +2544,7 @@ static int monitor_fdset_dup_fd_find_remove(int dup_fd, bool remove)
>                          monitor_fdset_cleanup(mon_fdset);
>                      }
>                  }
> -                return mon_fdset->id;
> +                return id;
>              }
>          }
>      }

If monitor_fdset_cleanup closes the FD won't you now be passing an
invalid fd to the calling function?


-- 
Alex Bennée

  reply	other threads:[~2014-08-04  9:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  8:25 [Qemu-devel] [PATCH 0/4] fix several bugs about use-after-free and an api abuse zhanghailiang
2014-08-04  8:25 ` [Qemu-devel] [PATCH 1/4] l2cap: fix access freed memory zhanghailiang
2014-08-04  8:37   ` Alex Bennée
2014-08-04  8:25 ` [Qemu-devel] [PATCH 2/4] monitor: " zhanghailiang
2014-08-04  9:01   ` Alex Bennée [this message]
2014-08-05  2:37     ` zhanghailiang
2014-08-04  8:25 ` [Qemu-devel] [PATCH 3/4] virtio-blk: fix reference a pointer which might be freed zhanghailiang
2014-08-04 11:14   ` Stefan Hajnoczi
2014-08-04  8:25 ` [Qemu-devel] [PATCH 4/4] ivshmem: check the value returned by fstat() zhanghailiang
2014-08-04 12:26   ` Michael S. Tsirkin
2014-08-05  2:00     ` zhanghailiang
2014-08-05  6:50       ` Levente Kurusa
2014-08-05  7:08         ` zhanghailiang
2014-08-05 10:00       ` Michael S. Tsirkin

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=87fvhcvdam.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=alex@alex.org.uk \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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).