From: Russell Currey <ruscur@russell.cc>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [1/3] powerpc/eeh: Null check uses of eeh_pe_bus_get
Date: Wed, 21 Sep 2016 14:06:23 +1000 [thread overview]
Message-ID: <1474430783.3091.10.camel@russell.cc> (raw)
In-Reply-To: <3sf5YS0BVKz9sxN@ozlabs.org>
On Wed, 2016-09-21 at 14:02 +1000, Michael Ellerman wrote:
> On Mon, 2016-12-09 at 04:17:22 UTC, Russell Currey wrote:
> >
> > eeh_pe_bus_get() can return NULL if a PCI bus isn't found for a given PE.
> > Some callers don't check this, and can cause a null pointer dereference
> > under certain circumstances.
> >
> > Fix this by checking NULL everywhere eeh_pe_bus_get() is called.
> >
> > Cc: stable #3.10+
>
> This looks like it's a fix for 8a6b1bc70dbb ("powerpc/eeh: EEH core to handle
> special event") ?
>
> Which was merged in v3.11-rc1.
>
> If so I'll add a fixes line pointing at that commit and update the stable tag
> to
> v3.11+.
Thanks.
Also, the other two patches in this series shouldn't go to stable, that was my
mistake.
>
> cheers
next prev parent reply other threads:[~2016-09-21 4:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 4:17 [PATCH 1/3] powerpc/eeh: Null check uses of eeh_pe_bus_get Russell Currey
2016-09-12 4:17 ` [PATCH 2/3] powernv/eeh: Skip finding bus for VF resets Russell Currey
2016-09-12 4:43 ` Andrew Donnellan
2016-09-12 4:17 ` [PATCH 3/3] powerpc/eeh: Skip finding bus until after failure reporting Russell Currey
2016-09-12 4:41 ` Andrew Donnellan
2016-09-12 4:39 ` [PATCH 1/3] powerpc/eeh: Null check uses of eeh_pe_bus_get Andrew Donnellan
2016-09-21 4:02 ` [1/3] " Michael Ellerman
2016-09-21 4:06 ` Russell Currey [this message]
2016-09-25 3:00 ` Michael Ellerman
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=1474430783.3091.10.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).