All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <artem.bityutskiy@linux.intel.com>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: fix random pointer dereference in OF device name handling
Date: Mon, 4 Feb 2013 10:03:53 -0500	[thread overview]
Message-ID: <510FCDD9.7060900@windriver.com> (raw)
In-Reply-To: <1359965101.13791.11.camel@sauron.fi.intel.com>

On 13-02-04 03:05 AM, Artem Bityutskiy wrote:
> On Wed, 2013-01-23 at 13:59 -0500, Paul Gortmaker wrote:
>> Here is the output from an mpc8548 based board.  There are
>> three instances of missing device name here:
> 
> A similar fix is already in the linux-mtd.git tree.

OK, I see it in linux-next for 3.9 (commit 7dfe4be351e816) but
it needs to get to mainline/Linus before 3.8 gets released,
since that is where the regression is introduced (and that
is why I ended up not seeing the fix, and redoing it, as
I was working off of mainline).

$ git describe --contains d68cbdd4fb
v3.8-rc1~47^2~53

Thanks,
Paul.


> 

WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <artem.bityutskiy@linux.intel.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: fix random pointer dereference in OF device name handling
Date: Mon, 4 Feb 2013 10:03:53 -0500	[thread overview]
Message-ID: <510FCDD9.7060900@windriver.com> (raw)
In-Reply-To: <1359965101.13791.11.camel@sauron.fi.intel.com>

On 13-02-04 03:05 AM, Artem Bityutskiy wrote:
> On Wed, 2013-01-23 at 13:59 -0500, Paul Gortmaker wrote:
>> Here is the output from an mpc8548 based board.  There are
>> three instances of missing device name here:
> 
> A similar fix is already in the linux-mtd.git tree.

OK, I see it in linux-next for 3.9 (commit 7dfe4be351e816) but
it needs to get to mainline/Linus before 3.8 gets released,
since that is where the regression is introduced (and that
is why I ended up not seeing the fix, and redoing it, as
I was working off of mainline).

$ git describe --contains d68cbdd4fb
v3.8-rc1~47^2~53

Thanks,
Paul.


> 

  reply	other threads:[~2013-02-04 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 18:59 [PATCH] mtd: fix random pointer dereference in OF device name handling Paul Gortmaker
2013-01-23 18:59 ` Paul Gortmaker
2013-02-04  8:05 ` Artem Bityutskiy
2013-02-04  8:05   ` Artem Bityutskiy
2013-02-04 15:03   ` Paul Gortmaker [this message]
2013-02-04 15:03     ` Paul Gortmaker

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=510FCDD9.7060900@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=plagnioj@jcrosoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.