All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Huangpeng \(Peter\)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-trivial] [PATCH 0/2] xen_pt: fix two Coverity defects
Date: Mon, 9 Feb 2015 10:37:36 +0800	[thread overview]
Message-ID: <54D81D70.8060508@huawei.com> (raw)
In-Reply-To: <1422689277-16032-1-git-send-email-arei.gonglei@huawei.com>

On 2015/1/31 15:27, Gonglei (Arei) wrote:

> From: Gonglei <arei.gonglei@huawei.com>
> 
> 
> Gonglei (2):
>   xen-pt: fix Negative array index read
>   xen-pt: fix Out-of-bounds read
> 
>  hw/xen/xen_pt_config_init.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 

Ping...

Regards,
-Gonglei



WARNING: multiple messages have this Message-ID (diff)
From: Gonglei <arei.gonglei@huawei.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] xen_pt: fix two Coverity defects
Date: Mon, 9 Feb 2015 10:37:36 +0800	[thread overview]
Message-ID: <54D81D70.8060508@huawei.com> (raw)
In-Reply-To: <1422689277-16032-1-git-send-email-arei.gonglei@huawei.com>

On 2015/1/31 15:27, Gonglei (Arei) wrote:

> From: Gonglei <arei.gonglei@huawei.com>
> 
> 
> Gonglei (2):
>   xen-pt: fix Negative array index read
>   xen-pt: fix Out-of-bounds read
> 
>  hw/xen/xen_pt_config_init.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 

Ping...

Regards,
-Gonglei

  parent reply	other threads:[~2015-02-09  2:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31  7:27 [Qemu-trivial] [PATCH 0/2] xen_pt: fix two Coverity defects arei.gonglei
2015-01-31  7:27 ` [Qemu-devel] " arei.gonglei
2015-01-31  7:27 ` [Qemu-trivial] [PATCH 1/2] xen-pt: fix Negative array index read arei.gonglei
2015-01-31  7:27   ` [Qemu-devel] " arei.gonglei
2015-02-10  6:40   ` [Qemu-trivial] " Stefano Stabellini
2015-02-10  6:40     ` [Qemu-devel] " Stefano Stabellini
2015-01-31  7:27 ` [Qemu-trivial] [PATCH 2/2] xen-pt: fix Out-of-bounds read arei.gonglei
2015-01-31  7:27   ` [Qemu-devel] " arei.gonglei
2015-02-10  6:39   ` [Qemu-trivial] " Stefano Stabellini
2015-02-10  6:39     ` [Qemu-devel] " Stefano Stabellini
2015-02-10  6:49     ` [Qemu-trivial] " Gonglei
2015-02-10  6:49       ` [Qemu-devel] " Gonglei
2015-02-10  7:00       ` [Qemu-trivial] " Stefano Stabellini
2015-02-10  7:00         ` [Qemu-devel] " Stefano Stabellini
2015-02-10  7:19         ` [Qemu-trivial] " Gonglei
2015-02-10  7:19           ` [Qemu-devel] " Gonglei
2015-02-09  2:37 ` Gonglei [this message]
2015-02-09  2:37   ` [Qemu-devel] [PATCH 0/2] xen_pt: fix two Coverity defects Gonglei
2015-02-10 18:52   ` [Qemu-trivial] " Michael Tokarev
2015-02-10 18:52     ` [Qemu-devel] " Michael Tokarev

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=54D81D70.8060508@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.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 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.