public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Kieser <peter@kieser.ca>
To: Slava Pestov <sp@datera.io>, Larkin Lowrey <llowrey@nuclearwinter.com>
Cc: Kent Overstreet <kmo@daterainc.com>, linux-bcache@vger.kernel.org
Subject: Re: Null pointer oops
Date: Fri, 15 Aug 2014 22:48:07 -0700	[thread overview]
Message-ID: <53EEF097.20002@kieser.ca> (raw)
In-Reply-To: <CACHGV4LtxvPz=VrzsXb9L2c779QijzQO-moPzM188AaVr8Q9jg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]


On 2014-08-13 2:30 PM, Slava Pestov wrote:
> I was mistaken. The bug is fixed in the pull request Kent sent to Jens for 3.16:
>
> http://evilpiepirate.org/git/linux-bcache.git/commit/?h=bcache-dev&id=bcf090e0040e30f8409e6a535a01e6473afb096f
(Again) are these fixes going to be backported to Linux 3.10 (or other 
longterm kernels?)

-Peter


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4504 bytes --]

  parent reply	other threads:[~2014-08-16  5:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  5:02 Null pointer oops Larkin Lowrey
     [not found] ` <CALJ65z=25CrrO9uMc2vfYVAQWb=6eK+OhB5TGJJrCp=D4ALvrQ@mail.gmail.com>
2014-08-13 16:40   ` Larkin Lowrey
2014-08-13 17:41     ` Slava Pestov
2014-08-13 18:35       ` Larkin Lowrey
2014-08-13 18:45         ` Slava Pestov
2014-08-13 21:21           ` Larkin Lowrey
2014-08-13 21:25             ` Slava Pestov
2014-08-13 21:30               ` Slava Pestov
2014-08-13 21:34                 ` Jianjian Huo
2014-08-13 22:14                 ` Larkin Lowrey
2014-08-16  5:48                 ` Peter Kieser [this message]
2014-08-13 21:32               ` Larkin Lowrey
2014-08-13 21:37                 ` Slava Pestov

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=53EEF097.20002@kieser.ca \
    --to=peter@kieser.ca \
    --cc=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=llowrey@nuclearwinter.com \
    --cc=sp@datera.io \
    /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