From: Greg KH <greg@kroah.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: stable <stable@vger.kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Ben Skeggs <bskeggs@redhat.com>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: Backport request for commit 579b7c582 (drm/nouveau/pmu: do not assume a PMU is present)
Date: Sun, 14 Feb 2016 14:12:01 -0800 [thread overview]
Message-ID: <20160214221201.GA9713@kroah.com> (raw)
In-Reply-To: <CAKb7UvgS0E6G6s5QuFJeFm54+fhB66BOcfTXfrsAhuw-29fSpw@mail.gmail.com>
On Wed, Jan 06, 2016 at 09:23:20AM -0500, Ilia Mirkin wrote:
> This commit should be backported to kernel 4.3 (apologies for
> line-wrapping). Without it, we get a null deref (i.e. oops) on GF117
> GPUs which for one reason or another don't have the PMU hooked up.
> That should be fixed in its own right, but that's a separate matter.
> The issue was introduced in commit e2ca4e7d6e (drm/nouveau/pmu:
> convert to new-style nvkm_subdev)
>
> commit 579b7c58215329803ce184704463de09f0f310ac
> Author: Alexandre Courbot <acourbot@nvidia.com>
> Date: Thu Sep 3 17:39:52 2015 +0900
>
> drm/nouveau/pmu: do not assume a PMU is present
>
> Some devices may not have a PMU. Avoid a NULL pointer dereference in
> such cases by checking whether the pointer given to nvkm_pmu_pgob() is
> valid.
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
>
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2016-02-14 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 14:23 Backport request for commit 579b7c582 (drm/nouveau/pmu: do not assume a PMU is present) Ilia Mirkin
2016-02-14 22:12 ` Greg KH [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=20160214221201.GA9713@kroah.com \
--to=greg@kroah.com \
--cc=acourbot@nvidia.com \
--cc=bskeggs@redhat.com \
--cc=imirkin@alum.mit.edu \
--cc=nouveau@lists.freedesktop.org \
--cc=stable@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