linux-kernel - Re: Bcache fixes for stable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130826232333.GA11778@moria.home.lan>
Date:	Mon, 26 Aug 2013 16:23:33 -0700
From:	Kent Overstreet <kmo@...erainc.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	stable@...r.kernel.org, linux-bcache@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Bcache fixes for stable

On Mon, Aug 26, 2013 at 03:19:57PM -0700, Greg Kroah-Hartman wrote:
> 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?

5c694129c8db6d89c9be109049a16510b2f70f6d
e49c7c374e7aacd1f04ecbc21d9dbbeeea4a77d6

> 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...

*nod* I need to get some more signatures on my gpg key...

> 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.

Ok, I'll remember that for the future.

> For now, I can edit these two patches and add them in, if you give me
> the git commit ids to verify them.

Ok - I don't care too much either way but there were some slightly
nontrivial conflicts on the second patch, and the one I did backported
has been tested.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/