From: Greg KH <greg@kroah.com>
To: dsterba@suse.cz, stable@vger.kernel.org,
linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: Btrfs stable updates for 3.16.x (and others)
Date: Wed, 3 Sep 2014 14:32:09 -0700 [thread overview]
Message-ID: <20140903213209.GA20589@kroah.com> (raw)
In-Reply-To: <20140819111045.GQ1553@suse.cz>
On Tue, Aug 19, 2014 at 01:10:45PM +0200, David Sterba wrote:
> Hi stable team,
>
> please add the following patches to stable trees.
>
> Patch #3 applies to all currently live stables, a 7 years old bug. I've
> briefly reviewed all 3 patches against 3.10/12/14/16 (ie. 3.4 skips #1
> and #2).
>
> Subjects:
> Btrfs: read lock extent buffer while walking backrefs
> Btrfs: fix compressed write corruption on enospc
> Btrfs: fix csum tree corruption, duplicate and outdated checksums
> Commits:
> 6f7ff6d7832c6be13e8c95598884dbc40ad69fb7
This doesn't apply to 3.10-stable :(
> ce62003f690dff38d3164a632ec69efa15c32cbf
Neither did this.
> 27b9a8122ff71a8cadfbffb9c4f0694300464f3b
Was already marked for stable.
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-03 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 11:10 Btrfs stable updates for 3.16.x (and others) David Sterba
2014-09-02 15:54 ` David Sterba
2014-09-03 21:32 ` Greg KH [this message]
2014-09-04 16:37 ` David Sterba
2014-09-04 21:56 ` Greg KH
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=20140903213209.GA20589@kroah.com \
--to=greg@kroah.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.