From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kent Overstreet <kmo@daterainc.com>
Cc: stable@vger.kernel.org, linux-bcache@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Bcache fixes for stable
Date: Mon, 26 Aug 2013 15:19:57 -0700 [thread overview]
Message-ID: <20130826221957.GA2782@kroah.com> (raw)
In-Reply-To: <20130826220249.GF2798@kmo-pixel>
On Mon, Aug 26, 2013 at 03:02:49PM -0700, Kent Overstreet wrote:
> Two fixes that went into 3.11 should've been marked for stable, but I
> screwed up and forgot to mark them.
>
> One of them fixes bugs that appear to being hit in the wild, so please
> pull these:
>
> The following changes since commit 0a4b6d4ff200a553951f77f765971cb3e4c91ec0:
>
> Linux 3.10.9 (2013-08-20 15:40:47 -0700)
>
> are available in the git repository at:
>
> git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-3.10
>
> for you to fetch changes up to a213846fafcdf52153dfebf8b1671498a72b6285:
>
> bcache: FUA fixes (2013-08-26 14:56:52 -0700)
>
> ----------------------------------------------------------------
> Kent Overstreet (1):
> bcache: FUA fixes
>
> Kumar Amit Mehta (1):
> md: bcache: io.c: fix a potential NULL pointer dereference
Can I get a hint as to what the git commit ids of these patches are in
Linus's tree?
Ideally, that's all you need to send me, but if you want to send me a
git pull, that's fine too, but please use a signed tag, otherwise it's
just a random tree...
Also, if you do a git pull, I need the git commit ids in the changelog
entry that match Linus's tree, so people (like me) can verify things.
For now, I can edit these two patches and add them in, if you give me
the git commit ids to verify them.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-26 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 22:02 Bcache fixes for stable Kent Overstreet
2013-08-26 22:19 ` Greg Kroah-Hartman [this message]
[not found] ` <20130826221957.GA2782-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-08-26 23:23 ` Kent Overstreet
[not found] ` <20130826232333.GA11778-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-08-27 0:47 ` Greg Kroah-Hartman
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=20130826221957.GA2782@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox