From: Stefan Hajnoczi <stefanha@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tests/libqos: Check for valid dev pointer when looking for PCI devices
Date: Tue, 27 Feb 2018 16:27:06 +0000 [thread overview]
Message-ID: <20180227162706.GE32480@stefanha-x1.localdomain> (raw)
In-Reply-To: <1519713884-2346-1-git-send-email-thuth@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Tue, Feb 27, 2018 at 07:44:44AM +0100, Thomas Huth wrote:
> dev could be NULL if the PCI device can not be found due to some
> reasons, so we must not dereference the pointer in this case.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/libqos/virtio-pci.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
There is no maintainer for tests/libqos/virtio-pci.c in MAINTAINERS so
I'll take this patch.
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-02-27 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 6:44 [Qemu-devel] [PATCH] tests/libqos: Check for valid dev pointer when looking for PCI devices Thomas Huth
2018-02-27 16:27 ` Stefan Hajnoczi [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=20180227162706.GE32480@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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).