All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Josh Durgin <josh.durgin@dreamhost.com>
Cc: qemu-devel@nongnu.org, ceph-devel@vger.kernel.org, chb@muc.de
Subject: Re: [PATCH] rbd: always set out parameter in qemu_rbd_snap_list
Date: Wed, 07 Dec 2011 11:27:48 +0100	[thread overview]
Message-ID: <4EDF3FA4.7060601@redhat.com> (raw)
In-Reply-To: <1323219910-17021-1-git-send-email-josh.durgin@dreamhost.com>

Am 07.12.2011 02:05, schrieb Josh Durgin:
> The caller expects psn_tab to be NULL when there are no snapshots or
> an error occurs. This results in calling g_free on an invalid address.
> 
> Reported-by: Oliver Francke <Oliver@filoo.de>
> Signed-off-by: Josh Durgin <josh.durgin@dreamhost.com>

Thanks, applied to the block branch.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Josh Durgin <josh.durgin@dreamhost.com>
Cc: ceph-devel@vger.kernel.org, qemu-devel@nongnu.org, chb@muc.de
Subject: Re: [Qemu-devel] [PATCH] rbd: always set out parameter in qemu_rbd_snap_list
Date: Wed, 07 Dec 2011 11:27:48 +0100	[thread overview]
Message-ID: <4EDF3FA4.7060601@redhat.com> (raw)
In-Reply-To: <1323219910-17021-1-git-send-email-josh.durgin@dreamhost.com>

Am 07.12.2011 02:05, schrieb Josh Durgin:
> The caller expects psn_tab to be NULL when there are no snapshots or
> an error occurs. This results in calling g_free on an invalid address.
> 
> Reported-by: Oliver Francke <Oliver@filoo.de>
> Signed-off-by: Josh Durgin <josh.durgin@dreamhost.com>

Thanks, applied to the block branch.

Kevin

  reply	other threads:[~2011-12-07 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  1:05 [PATCH] rbd: always set out parameter in qemu_rbd_snap_list Josh Durgin
2011-12-07  1:05 ` [Qemu-devel] " Josh Durgin
2011-12-07 10:27 ` Kevin Wolf [this message]
2011-12-07 10:27   ` Kevin Wolf

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=4EDF3FA4.7060601@redhat.com \
    --to=kwolf@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chb@muc.de \
    --cc=josh.durgin@dreamhost.com \
    --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.