public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuah.khan@hp.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Hugh Dickins <hughd@google.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel NULL pointer dereference at rb_erase+0x1a3/0x370
Date: Tue, 02 Oct 2012 15:20:44 -0600	[thread overview]
Message-ID: <1349212844.3141.52.camel@lorien2> (raw)
In-Reply-To: <20121002211007.GB15277@thunk.org>

On Tue, 2012-10-02 at 17:10 -0400, Theodore Ts'o wrote:
> The patch series in question has already been dropped, since there
> were some other problems found and we decided it wasn't ready for this
> merge window.
> 
> If you look at the latest linux-next branch, you'll see that those
> patches are gone, so it should be good once you upgrade to the latest
> linux-next.
> 
> 						- Ted

Great thanks.

-- Shuah


  reply	other threads:[~2012-10-02 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 17:58 kernel NULL pointer dereference at rb_erase+0x1a3/0x370 Shuah Khan
2012-10-02 20:27 ` Hugh Dickins
2012-10-02 21:10   ` Theodore Ts'o
2012-10-02 21:20     ` Shuah Khan [this message]
2012-10-02 21:33   ` Shuah Khan

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=1349212844.3141.52.camel@lorien2 \
    --to=shuah.khan@hp.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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