linux-kernel - Re: [GIT PULL] bcache changes for 3.17

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: <540A44A3.5060502@kieser.ca>
Date:	Fri, 05 Sep 2014 16:17:55 -0700
From:	Peter Kieser <peter@...ser.ca>
To:	Greg KH <greg@...ah.com>, Francis Moreau <francis.moro@...il.com>
CC:	Jens Axboe <axboe@...nel.dk>, Kent Overstreet <kmo@...erainc.com>,
	linux-kernel@...r.kernel.org, linux-bcache@...r.kernel.org,
	stable <stable@...r.kernel.org>
Subject: Re: [GIT PULL] bcache changes for 3.17


On 2014-09-05 2:45 PM, Greg KH wrote:
> Just because a maintainer/developer doesn't want to do anything for the
> stable kernel releases does_NOT_  mean the code is
> "unstable/expreimental" at all.

These are more bcache-ate-my-data unstable bugs. It's standard practice 
to backport fixes that cause instability/data corruption to a 'stable' 
release (otherwise, why would it be named 'stable')?

-Peter


Download attachment "smime.p7s" of type "application/pkcs7-signature" (4291 bytes)