linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Colin King <colin.king@canonical.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: cbe-oss-dev@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org,
	Colin Ian King <colin.king@canonical.com>
Subject: Re: [2/3] drivers/ps3: Fix ps3-vuart null dereference
Date: Fri,  2 Oct 2015 17:47:09 +1000 (AEST)	[thread overview]
Message-ID: <20151002074709.8EF71140316@ozlabs.org> (raw)
In-Reply-To: <497c718e763173b28ffe4e50258cb257c362d404.1442259101.git.geoff@infradead.org>

On Mon, 2015-14-09 at 19:35:04 UTC, Colin King wrote:
> On the unlikely event that drv is null, the current code will
> perform a null pointer dereference with it when printing a dev_dbg
> message.  Instead, the BUG_ON check on drv should be performed
> before we emit the dev_dbg message.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> Signed-off-by: Geoff Levand <geoff@infradead.org>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/6a6120bc5ec9e54d3cc06e73

cheers

  parent reply	other threads:[~2015-10-02  7:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 19:35 [PATCH 0/3] PS3 updates for 4.3 Geoff Levand
2015-09-14 19:35 ` [PATCH 2/3] drivers/ps3: Fix ps3-vuart null dereference Colin Ian King
2015-09-15 10:37   ` David Laight
2015-10-02  7:47   ` Michael Ellerman [this message]
2015-09-14 19:35 ` [PATCH 1/3] drivers/ps3: Fix ps3-lpm white space Rudhresh Kumar J
2015-10-02  7:47   ` [1/3] " Michael Ellerman
2015-09-14 19:35 ` [PATCH 3/3] powerpc/ps3: Refresh ps3_defconfig Geoff Levand
2015-09-14 20:13   ` [Cbe-oss-dev] " Geert Uytterhoeven
2015-09-14 21:36   ` [PATCH V2 " Geoff Levand
2015-10-02  7:47     ` [V2,3/3] " 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=20151002074709.8EF71140316@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=cbe-oss-dev@lists.ozlabs.org \
    --cc=colin.king@canonical.com \
    --cc=linuxppc-dev@lists.ozlabs.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).