From: Borislav Petkov <bp@alien8.de>
To: John <da_audiophile@yahoo.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"mlindner@marvell.com" <mlindner@marvell.com>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [BUG] unable to handle kernel NULL pointer dereference
Date: Mon, 17 Feb 2014 21:30:57 +0100 [thread overview]
Message-ID: <20140217203057.GJ4559@pd.tnic> (raw)
In-Reply-To: <1392667974.22806.YahooMailNeo@web140003.mail.bf1.yahoo.com>
On Mon, Feb 17, 2014 at 12:12:54PM -0800, John wrote:
> Trond. Yes, your patch fixes the regression for me; tested on
> v3.13.3, I do not know the process by which patches get into
> the next stable release (minor version). My hope is that once
> peer-reviewed, this patch gets into the 3.13.4 and since the 3.12
> series is not EOL yet, into 3.12.12 as well. Thank you for the time
> and effort!
Basically you say
Tested-by: John <da_audiophile@yahoo.com>
Trond adds stable to CC, sends it to Linus and it trickles down to
3.12.x and 3.13.x stable.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-02-17 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 12:10 [BUG] unable to handle kernel NULL pointer dereference John
2014-02-15 20:08 ` John
2014-02-15 20:30 ` Borislav Petkov
2014-02-15 21:04 ` John
2014-02-15 23:25 ` Borislav Petkov
2014-02-16 2:09 ` John
2014-02-16 17:27 ` Trond Myklebust
2014-02-16 17:35 ` Borislav Petkov
2014-02-17 20:12 ` John
2014-02-17 20:30 ` Borislav Petkov [this message]
2014-02-17 20:35 ` John
-- strict thread matches above, loose matches on Subject: below --
2008-07-21 18:32 Thomas Meyer
2007-10-22 17:17 [BUG] Unable " Daniel Cid
2007-10-22 17:24 ` Ray Lee
2007-10-29 7:42 ` Andrew Morton
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=20140217203057.GJ4559@pd.tnic \
--to=bp@alien8.de \
--cc=bfields@fieldses.org \
--cc=da_audiophile@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mlindner@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=trond.myklebust@primarydata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox