From: Paolo Bonzini <pbonzini@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: qemu-devel@nongnu.org, Ling Liu <liuling-it@360.cn>
Subject: Re: [Qemu-devel] [PATCH] i386: avoid null pointer dereference
Date: Thu, 7 Jan 2016 13:38:47 +0100 [thread overview]
Message-ID: <568E5C57.7090309@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1601042116500.18576@wniryva>
On 04/01/2016 16:49, P J P wrote:
> +-- On Fri, 18 Dec 2015, P J P wrote --+
> | A null pointer dereference issue was reported by Mr Ling Liu, CC'd here. It
> | occurs while doing I/O port write operations via hmp interface. In that,
> | 'current_cpu' remains null as it is not called from cpu_exec loop, which
> | results in the said issue.
>
> Ping..! -> https://patchwork.ozlabs.org/patch/558748/
I was on vacation until today. I'll send a pull request some time next
week.
Paolo
next prev parent reply other threads:[~2016-01-07 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 6:05 [Qemu-devel] [PATCH] i386: avoid null pointer dereference P J P
2016-01-04 15:49 ` P J P
2016-01-07 12:38 ` Paolo Bonzini [this message]
2016-01-07 13:30 ` P J P
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=568E5C57.7090309@redhat.com \
--to=pbonzini@redhat.com \
--cc=liuling-it@360.cn \
--cc=ppandit@redhat.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 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).