From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: mcrossley@nvidia.com, Kirti Wankhede <kwankhede@nvidia.com>,
Neo Jia <cjia@nvidia.com>,
QEMU Developers <qemu-devel@nongnu.org>,
dnigam@nvidia.com
Subject: Re: [PATCH v2 1/1] Fix use after free in vfio_migration_probe
Date: Thu, 12 Nov 2020 09:59:08 -0700 [thread overview]
Message-ID: <20201112095908.77d711e7@w520.home> (raw)
In-Reply-To: <CAFEAcA8orN-NPghL+LW1jmQ0bjjQbGYctCc2_1S1q+Mcy=rEtA@mail.gmail.com>
On Thu, 12 Nov 2020 15:57:46 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> On Fri, 6 Nov 2020 at 18:35, Kirti Wankhede <kwankhede@nvidia.com> wrote:
> >
> > Fixes Coverity issue:
> > CID 1436126: Memory - illegal accesses (USE_AFTER_FREE)
> >
> > Fixes: a9e271ec9b36 ("vfio: Add migration region initialization and finalize
> > function")
> >
> > Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> > Reviewed-by: David Edmondson <dme@dme.org>
> > Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> > Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> > ---
>
> Hi Alex -- this is a fix for a Coverity issue, are you planning
> a pullreq with it in? It would be nice to have it in rc2 next week.
Hi Peter,
Yes, I was planning to send a pull request. It's a trivial and obvious
fix, so if by chance you'd like to grab it separately, you're also more
than welcome.
Acked-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
Thanks,
Alex
prev parent reply other threads:[~2020-11-12 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 18:02 [PATCH v2 1/1] Fix use after free in vfio_migration_probe Kirti Wankhede
2020-11-12 15:57 ` Peter Maydell
2020-11-12 16:59 ` Alex Williamson [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=20201112095908.77d711e7@w520.home \
--to=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=dnigam@nvidia.com \
--cc=kwankhede@nvidia.com \
--cc=mcrossley@nvidia.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).