From: Alex Williamson <alex.williamson@redhat.com>
To: Schspa Shi <schspa@gmail.com>
Cc: cohuck@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vfio: Clear the caps->buf to NULL after free
Date: Tue, 28 Jun 2022 09:50:13 -0600 [thread overview]
Message-ID: <20220628095013.266d4a40.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220628152429.286-1-schspa@gmail.com>
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);
> }
next prev parent reply other threads:[~2022-06-28 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 15:24 Schspa Shi
2022-06-28 15:50 ` Alex Williamson [this message]
2022-06-28 15:58 ` Cornelia Huck
2022-06-29 4:51 ` Schspa Shi
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=20220628095013.266d4a40.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schspa@gmail.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
all inboxes | Powered by JetHome®