From: Bronek Kozicki <brok@spamcop.net>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: Test for PCI root bus to avoid NULL pointer dereference
Date: Fri, 03 Oct 2014 19:01:20 +0100 [thread overview]
Message-ID: <542EE470.9050700@spamcop.net> (raw)
In-Reply-To: <20140827185651.29388.16082.stgit@gimli.home>
On 27/08/2014 19:57, Alex Williamson wrote:
> If we have a GPU on the PCI root bus that calls
> drm_pcie_get_speed_cap_mask() we end up with a NULL pointer
> dereference since pdev->bus->self is NULL. We already protect
> against callers passing non-PCI devices, so let's also catch this
> case and return -EINVAL.
>
> Root complex graphics are not terribly likely outside of IGD, but
> when we assign a standard plugin GPU to a virtual machine, our
> assumption that we have a parent device quickly becomes invalid.
What happend to this patch? I don't see it applied on
https://github.com/torvalds/linux/tree/master/drivers/gpu/drm
B.
prev parent reply other threads:[~2014-10-03 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 18:57 [PATCH] drm: Test for PCI root bus to avoid NULL pointer dereference Alex Williamson
2014-08-27 19:01 ` Alex Deucher
2014-10-03 18:01 ` Bronek Kozicki [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=542EE470.9050700@spamcop.net \
--to=brok@spamcop.net \
--cc=alex.williamson@redhat.com \
--cc=linux-kernel@vger.kernel.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).