From: Laszlo Ersek <lersek@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>, P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Qinghao Tang <luodalongde@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Prasad J Pandit <pjp@fedoraproject.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] virtio: add check for descriptor's mapped address
Date: Mon, 19 Sep 2016 19:25:29 +0200 [thread overview]
Message-ID: <5117e2fb-2658-dbb7-cbdd-e8fe9ee14880@redhat.com> (raw)
In-Reply-To: <11a29d88-2e4d-d016-6a44-de5d7c6cbe57@redhat.com>
On 09/19/16 19:16, Laurent Vivier wrote:
>
>
> On 19/09/2016 18:59, Laszlo Ersek wrote:
>> On 09/19/16 17:55, Stefan Hajnoczi wrote:
>>> On Mon, Sep 19, 2016 at 02:36:11PM +0530, P J P wrote:
>>>> From: Prasad J Pandit <pjp@fedoraproject.org>
>>>>
>>>> virtio back end uses set of buffers to facilitate I/O operations.
>>>> If its size is too large, 'cpu_physical_memory_map' could return
>>>> a null address. This would result in a null dereference while
>>>> un-mapping descriptors. Add check to avoid it.
>>>>
>>>> Reported-by: Qinghao Tang <luodalongde@gmail.com>
>>>> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
>>>> ---
>>>> hw/virtio/virtio.c | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>>>>
>>>> Update per:
>>>> -> https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg03889.html
>>>>
>>>> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
>>>> index 15ee3a7..311dd0b 100644
>>>> --- a/hw/virtio/virtio.c
>>>> +++ b/hw/virtio/virtio.c
>>>> @@ -472,6 +472,11 @@ static void virtqueue_map_desc(unsigned int *p_num_sg, hwaddr *addr, struct iove
>>>> }
>>>>
>>>> iov[num_sg].iov_base = cpu_physical_memory_map(pa, &len, is_write);
>>>> + if (!iov[num_sg].iov_base) {
>>>> + error_report("virtio: bogus descriptor or out of resources");
>>>> + exit(EXIT_FAILURE);
>>>
>>> exit(1) is used everywhere else in the file (including just a few lines
>>> above in the same function). Please use exit(1) for consistency.
>>
>> Laurent's pending series
>>
>> [Qemu-devel] [PATCH 00/26] trivial: use exit(EXIT_SUCCESS) and
>> exit(EXIT_FAILURE)
>>
>> specifically his patch
>>
>> [Qemu-devel] [PATCH 11/26] pci, virtio: use exit(EXIT_SUCCESS) and
>> exit(EXIT_FAILURE)
>>
>> converts the argument of the exit() that you name to EXIT_FAILURE.
>>
>> So using EXIT_FAILURE in Prasad's patch is actually what will uphold
>> consistency.
>>
>>> Looks fine otherwise.
>>>
>
> Laszlo, it seems Peter (and some others) would prefer to use exit(1)
> instead of exit(EXIT_FAILURE), so I don't think my series will be applied.
Thanks for the information, Laurent!
Prasad, can you please send a v3 then, to address Stefan's feedback?
Thank you
Laszlo
next prev parent reply other threads:[~2016-09-19 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 9:06 [Qemu-devel] [PATCH v2] virtio: add check for descriptor's mapped address P J P
2016-09-19 10:37 ` Laszlo Ersek
2016-09-19 15:55 ` Stefan Hajnoczi
2016-09-19 16:59 ` Laszlo Ersek
2016-09-19 17:16 ` Laurent Vivier
2016-09-19 17:25 ` Laszlo Ersek [this message]
2016-09-19 18:26 ` 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=5117e2fb-2658-dbb7-cbdd-e8fe9ee14880@redhat.com \
--to=lersek@redhat.com \
--cc=luodalongde@gmail.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).