From: pannengyuan <pannengyuan@huawei.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: kuhn.chenqun@huawei.com, qemu-arm@nongnu.org,
kenny.zhangjun@huawei.com, qemu-devel@nongnu.org,
zhang.zhanghailiang@huawei.com
Subject: Re: [Qemu-devel][PATCH] ppc/spapr_events: fix potential NULL pointer dereference in rtas_event_log_dequeue
Date: Tue, 19 Nov 2019 11:11:39 +0800 [thread overview]
Message-ID: <3e289453-cde4-cb9c-882f-88a5a2e78b36@huawei.com> (raw)
In-Reply-To: <20191119025058.GN5582@umbus.fritz.box>
Thanks for you reply.
I think you are right, I will send a new version later.
On 2019/11/19 10:50, David Gibson wrote:
> On Mon, Nov 18, 2019 at 09:50:13AM +0800, pannengyuan@huawei.com wrote:
>> From: PanNengyuan <pannengyuan@huawei.com>
>>
>> source is being dereferenced before it is null checked, hence there is a
>> potential null pointer dereference.
>>
>> This fixes:
>> 360
>> CID 68911917: (NULL_RETURNS)
>> 361. dereference: Dereferencing "source", which is known to be
>> "NULL".
>> 361 if (source->mask & event_mask) {
>> 362 break;
>> 363 }
>>
>> Reported-by: Euler Robot <euler.robot@huawei.com>
>> Signed-off-by: PanNengyuan <pannengyuan@huawei.com>
>
> I don't think this is the right solution. The only events we ever
> generated are LOG_TYPE_EPOW and LOG_TYPE_HOTPLUG, so in fact source
> should never be NULL.
>
> I think the correct way to satisfy Coverity here is to have
> rtas_event_log_to_source() do an assert(), rather than returning NULL
> for other event types.
>
>> ---
>> hw/ppc/spapr_events.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/ppc/spapr_events.c b/hw/ppc/spapr_events.c
>> index 0e4c195..febd2ef 100644
>> --- a/hw/ppc/spapr_events.c
>> +++ b/hw/ppc/spapr_events.c
>> @@ -358,7 +358,7 @@ static SpaprEventLogEntry *rtas_event_log_dequeue(SpaprMachineState *spapr,
>> rtas_event_log_to_source(spapr,
>> spapr_event_log_entry_type(entry));
>>
>> - if (source->mask & event_mask) {
>> + if (source && (source->mask & event_mask)) {
>> break;
>> }
>> }
>
prev parent reply other threads:[~2019-11-19 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 1:50 [Qemu-devel][PATCH] ppc/spapr_events: fix potential NULL pointer dereference in rtas_event_log_dequeue pannengyuan
2019-11-19 2:50 ` David Gibson
2019-11-19 3:11 ` pannengyuan [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=3e289453-cde4-cb9c-882f-88a5a2e78b36@huawei.com \
--to=pannengyuan@huawei.com \
--cc=david@gibson.dropbear.id.au \
--cc=kenny.zhangjun@huawei.com \
--cc=kuhn.chenqun@huawei.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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).