* [PATCH v2] vfio: Clear the caps->buf to NULL after free
@ 2022-06-28 15:24 Schspa Shi
2022-06-28 15:50 ` Alex Williamson
0 siblings, 1 reply; 4+ messages in thread
From: Schspa Shi @ 2022-06-28 15:24 UTC (permalink / raw)
To: alex.williamson, cohuck; +Cc: kvm, linux-kernel, Schspa Shi
API vfio_info_cap_add will free caps->buf, clear it to NULL after
free.
Signed-off-by: Schspa Shi <schspa@gmail.com>
---
drivers/vfio/vfio.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
index 61e71c1154be..a0fb93866f61 100644
--- a/drivers/vfio/vfio.c
+++ b/drivers/vfio/vfio.c
@@ -1812,6 +1812,7 @@ struct vfio_info_cap_header *vfio_info_cap_add(struct vfio_info_cap *caps,
buf = krealloc(caps->buf, caps->size + size, GFP_KERNEL);
if (!buf) {
kfree(caps->buf);
+ caps->buf = NULL;
caps->size = 0;
return ERR_PTR(-ENOMEM);
}
--
2.24.3 (Apple Git-128)
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH v2] vfio: Clear the caps->buf to NULL after free
2022-06-28 15:24 [PATCH v2] vfio: Clear the caps->buf to NULL after free Schspa Shi
@ 2022-06-28 15:50 ` Alex Williamson
2022-06-28 15:58 ` Cornelia Huck
0 siblings, 1 reply; 4+ messages in thread
From: Alex Williamson @ 2022-06-28 15:50 UTC (permalink / raw)
To: Schspa Shi; +Cc: cohuck, kvm, linux-kernel
On Tue, 28 Jun 2022 23:24:29 +0800
Schspa Shi <schspa@gmail.com> wrote:
> API vfio_info_cap_add will free caps->buf, clear it to NULL after
> free.
Should this be something like:
On buffer resize failure, vfio_info_cap_add() will free the buffer,
report zero for the size, and return -ENOMEM. As additional
hardening, also clear the buffer pointer to prevent any chance of a
double free.
Thanks,
Alex
> Signed-off-by: Schspa Shi <schspa@gmail.com>
> ---
> drivers/vfio/vfio.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> index 61e71c1154be..a0fb93866f61 100644
> --- a/drivers/vfio/vfio.c
> +++ b/drivers/vfio/vfio.c
> @@ -1812,6 +1812,7 @@ struct vfio_info_cap_header *vfio_info_cap_add(struct vfio_info_cap *caps,
> buf = krealloc(caps->buf, caps->size + size, GFP_KERNEL);
> if (!buf) {
> kfree(caps->buf);
> + caps->buf = NULL;
> caps->size = 0;
> return ERR_PTR(-ENOMEM);
> }
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH v2] vfio: Clear the caps->buf to NULL after free
2022-06-28 15:50 ` Alex Williamson
@ 2022-06-28 15:58 ` Cornelia Huck
2022-06-29 4:51 ` Schspa Shi
0 siblings, 1 reply; 4+ messages in thread
From: Cornelia Huck @ 2022-06-28 15:58 UTC (permalink / raw)
To: Alex Williamson, Schspa Shi; +Cc: kvm, linux-kernel
On Tue, Jun 28 2022, Alex Williamson <alex.williamson@redhat.com> wrote:
> On Tue, 28 Jun 2022 23:24:29 +0800
> Schspa Shi <schspa@gmail.com> wrote:
>
>> API vfio_info_cap_add will free caps->buf, clear it to NULL after
>> free.
>
> Should this be something like:
>
> On buffer resize failure, vfio_info_cap_add() will free the buffer,
> report zero for the size, and return -ENOMEM. As additional
> hardening, also clear the buffer pointer to prevent any chance of a
> double free.
I like that better. With that,
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
> Thanks,
> Alex
>
>> Signed-off-by: Schspa Shi <schspa@gmail.com>
>> ---
>> drivers/vfio/vfio.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
>> index 61e71c1154be..a0fb93866f61 100644
>> --- a/drivers/vfio/vfio.c
>> +++ b/drivers/vfio/vfio.c
>> @@ -1812,6 +1812,7 @@ struct vfio_info_cap_header *vfio_info_cap_add(struct vfio_info_cap *caps,
>> buf = krealloc(caps->buf, caps->size + size, GFP_KERNEL);
>> if (!buf) {
>> kfree(caps->buf);
>> + caps->buf = NULL;
>> caps->size = 0;
>> return ERR_PTR(-ENOMEM);
>> }
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH v2] vfio: Clear the caps->buf to NULL after free
2022-06-28 15:58 ` Cornelia Huck
@ 2022-06-29 4:51 ` Schspa Shi
0 siblings, 0 replies; 4+ messages in thread
From: Schspa Shi @ 2022-06-29 4:51 UTC (permalink / raw)
To: Cornelia Huck; +Cc: Alex Williamson, kvm, linux-kernel
Cornelia Huck <cohuck@redhat.com> writes:
> On Tue, Jun 28 2022, Alex Williamson
> <alex.williamson@redhat.com> wrote:
>
>> On Tue, 28 Jun 2022 23:24:29 +0800
>> Schspa Shi <schspa@gmail.com> wrote:
>>
>>> API vfio_info_cap_add will free caps->buf, clear it to NULL
>>> after
>>> free.
>>
>> Should this be something like:
>>
>> On buffer resize failure, vfio_info_cap_add() will free the
>> buffer,
>> report zero for the size, and return -ENOMEM. As
>> additional
>> hardening, also clear the buffer pointer to prevent any
>> chance of a
>> double free.
>
> I like that better. With that,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
I have send a V3 patch for this comment change, please review it.
>>
>> Thanks,
>> Alex
>>
>>> Signed-off-by: Schspa Shi <schspa@gmail.com>
>>> ---
>>> drivers/vfio/vfio.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
>>> index 61e71c1154be..a0fb93866f61 100644
>>> --- a/drivers/vfio/vfio.c
>>> +++ b/drivers/vfio/vfio.c
>>> @@ -1812,6 +1812,7 @@ struct vfio_info_cap_header
>>> *vfio_info_cap_add(struct vfio_info_cap *caps,
>>> buf = krealloc(caps->buf, caps->size + size, GFP_KERNEL);
>>> if (!buf) {
>>> kfree(caps->buf);
>>> + caps->buf = NULL;
>>> caps->size = 0;
>>> return ERR_PTR(-ENOMEM);
>>> }
--
BRs
Schspa Shi
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-06-29 4:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-06-28 15:24 [PATCH v2] vfio: Clear the caps->buf to NULL after free Schspa Shi
2022-06-28 15:50 ` Alex Williamson
2022-06-28 15:58 ` Cornelia Huck
2022-06-29 4:51 ` Schspa Shi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox