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