All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: dev@dpdk.org, zhihong.wang@intel.com, jfreimann@redhat.com,
	stable@dpdk.org
Subject: Re: [PATCH] vhost: fix possible null pointer dereferencing
Date: Tue, 27 Nov 2018 10:52:00 +0100	[thread overview]
Message-ID: <79b2ea77-302d-9ca4-491f-408de32eeb29@redhat.com> (raw)
In-Reply-To: <20181127094409.GA20896@debian>



On 11/27/18 10:44 AM, Tiwei Bie wrote:
> On Tue, Nov 27, 2018 at 10:23:25AM +0100, Maxime Coquelin wrote:
>> If mmap() call fails in vhost_user_set_mem_table, dev->mem
>> is set to NULL. If later, qva_to_vva() is called, a segfault
>> occurs.
>>
>> Fixes: 8f972312b8f4 ("vhost: support vhost-user")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> ---
>>   lib/librte_vhost/vhost_user.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/lib/librte_vhost/vhost_user.c b/lib/librte_vhost/vhost_user.c
>> index 3ea64eba6..c44fef9cc 100644
>> --- a/lib/librte_vhost/vhost_user.c
>> +++ b/lib/librte_vhost/vhost_user.c
>> @@ -489,6 +489,9 @@ qva_to_vva(struct virtio_net *dev, uint64_t qva, uint64_t *len)
>>   	struct rte_vhost_mem_region *r;
>>   	uint32_t i;
>>   
>> +	if (unlikely(!dev || !dev->mem))
>> +		return 0;
> 
> Better to also zero *len.
> 
> Reviewed-by: Tiwei Bie <tiwei.bie@intel.com>

Right, I'll post a v2 zeroing *len.

Thanks,
Maxime

> 
>> +
>>   	/* Find the region where the address lives. */
>>   	for (i = 0; i < dev->mem->nregions; i++) {
>>   		r = &dev->mem->regions[i];
>> -- 
>> 2.17.2
>>

      reply	other threads:[~2018-11-27  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  9:23 [PATCH] vhost: fix possible null pointer dereferencing Maxime Coquelin
2018-11-27  9:44 ` Tiwei Bie
2018-11-27  9:52   ` Maxime Coquelin [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=79b2ea77-302d-9ca4-491f-408de32eeb29@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jfreimann@redhat.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=zhihong.wang@intel.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.