All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Stefan Priebe - Profihost AG
	<s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: kernel 3.10 + applied bcache patches unable to handle kernel NULL pointer dereference
Date: Fri, 12 Jul 2013 01:19:01 -0700	[thread overview]
Message-ID: <20130712081901.GB8339@kmo-pixel> (raw)
In-Reply-To: <51DF9E21.3060601-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>

On Fri, Jul 12, 2013 at 08:11:45AM +0200, Stefan Priebe - Profihost AG wrote:
> Am 12.07.2013 03:40, schrieb Kent Overstreet:
> > On Thu, Jul 04, 2013 at 01:45:42PM +0200, Stefan Priebe - Profihost AG wrote:
> >> fix is this one: http://pastebin.com/raw.php?i=LBFJRvEt
> > 
> > Oh I see, the patch that introduced this is an old version of the patch
> > - the bcache-for-3.11 had this fixed, and I forgot to update that
> > branch. Thanks, I'll apply it there.
> 
> thanks - which commit id is the fix in? i can't find it.

The patch that introduced it wasn't ever destined for 3.10 anyways, and
I just deleted the bcache/bcache-3.9 branches because they'd gotten out
of sync and weren't getting updated with bcache-dev/bcache-for-3.11.

So just stick with bcache-for-3.10, I just backported all the important
bugfixes to it - I'll be sending that stuff to Greg K-H for 3.10.1 in
the next couple days too.

  parent reply	other threads:[~2013-07-12  8:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  9:39 kernel 3.10 + applied bcache patches unable to handle kernel NULL pointer dereference Stefan Priebe - Profihost AG
     [not found] ` <51D542EB.7070404-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-04 11:45   ` Stefan Priebe - Profihost AG
     [not found]     ` <51D56066.80106-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  1:40       ` Kent Overstreet
2013-07-12  6:11         ` Stefan Priebe - Profihost AG
     [not found]           ` <51DF9E21.3060601-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  8:19             ` Kent Overstreet [this message]
2013-07-12  8:31               ` Stefan Priebe - Profihost AG
     [not found]                 ` <51DFBEEF.3020106-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  8:38                   ` Stefan Priebe - Profihost AG
     [not found]                     ` <51DFC087.4080402-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  8:42                       ` Stefan Priebe - Profihost AG
     [not found]                         ` <51DFC16D.60607-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  8:44                           ` Stefan Priebe - Profihost AG

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=20130712081901.GB8339@kmo-pixel \
    --to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.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 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.