From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alistair Popple <alistair@popple.id.au>
Cc: devicetree@vger.kernel.org,
Alistair Popple <alistair@popple.id.au>,
mhairgrove@nvidia.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, robh+dt@kernel.org,
shailendras@nvidia.com
Subject: Re: [v2, 2/3] powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev
Date: Thu, 6 Apr 2017 23:06:07 +1000 (AEST) [thread overview]
Message-ID: <3vzNHz2TyZz9sCX@ozlabs.org> (raw)
In-Reply-To: <1491213104-24450-2-git-send-email-alistair@popple.id.au>
On Mon, 2017-04-03 at 09:51:43 UTC, Alistair Popple wrote:
> The pnv_pci_get_{gpu|npu}_dev functions are used to find associations
> between nvlink PCIe devices and standard PCIe devices. However they
> lacked basic sanity checking which results in NULL pointer
> dereferencing if they are incorrect called can be harder to spot than
> an explicit WARN_ON.
>
> Signed-off-by: Alistair Popple <alistair@popple.id.au>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/4c3b89effc281704d5395282c800c4
cheers
next prev parent reply other threads:[~2017-04-06 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 9:51 [PATCH v2 1/3] drivers/of/base.c: Add of_property_read_u64_index Alistair Popple
2017-04-03 9:51 ` [PATCH v2 2/3] powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev Alistair Popple
2017-04-06 13:06 ` Michael Ellerman [this message]
2017-04-03 9:51 ` [PATCH v2 3/3] powerpc/powernv: Introduce address translation services for Nvlink2 Alistair Popple
2017-04-06 13:06 ` [v2, " Michael Ellerman
2017-04-06 13:06 ` [v2,1/3] drivers/of/base.c: Add of_property_read_u64_index 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=3vzNHz2TyZz9sCX@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=alistair@popple.id.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mhairgrove@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=shailendras@nvidia.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).