From: Greg KH <greg@kroah.com>
To: David Sterba <dsterba@suse.cz>
Cc: stable@vger.kernel.org
Subject: Re: Btrfs stable fixes for 4.5.x (with added commit references)
Date: Mon, 16 May 2016 18:12:12 -0700 [thread overview]
Message-ID: <20160517011212.GA4194@kroah.com> (raw)
In-Reply-To: <20160511124536.GB29353@suse.cz>
On Wed, May 11, 2016 at 02:45:36PM +0200, David Sterba wrote:
> Hi,
>
> (resending original text, patches with "commit SHA upstream." lines added to all patches)
>
> please queue the following patches to 4.5 stable. There are fixes for user
> visible bugs, improved error handling and stability fixes.
>
> There are 3 patches that do not apply directly to 4.5.3 so I'm sending the full
> patch set for ease of application.
>
> I have tested the patches on top of 4.5. Some patches may apply to older stable
> branches but haven't been tested nor reviewed in that respect.
All now applied to 4.5-stable, thanks.
greg k-h
prev parent reply other threads:[~2016-05-17 1:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 12:45 Btrfs stable fixes for 4.5.x (with added commit references) David Sterba
2016-05-11 12:47 ` [PATCH 01/17] btrfs: reada: Fix in-segment calculation for reada David Sterba
2016-05-11 12:47 ` [PATCH 02/17] Btrfs: fix truncate_space_check David Sterba
2016-05-11 12:47 ` [PATCH 03/17] btrfs: remove error message from search ioctl for nonexistent tree David Sterba
2016-05-11 12:47 ` [PATCH 04/17] btrfs: change max_inline default to 2048 David Sterba
2016-05-11 12:47 ` [PATCH 05/17] Btrfs: fix unreplayable log after snapshot delete + parent dir fsync David Sterba
2016-05-11 12:47 ` [PATCH 06/17] Btrfs: fix file loss on log replay after renaming a file and fsync David Sterba
2016-05-11 12:47 ` [PATCH 07/17] Btrfs: fix extent_same allowing destination offset beyond i_size David Sterba
2016-05-11 12:47 ` [PATCH 08/17] Btrfs: fix deadlock between direct IO reads and buffered writes David Sterba
2016-05-11 12:47 ` [PATCH 09/17] Btrfs: fix race when checking if we can skip fsync'ing an inode David Sterba
2016-05-11 12:47 ` [PATCH 10/17] Btrfs: do not collect ordered extents when logging that inode exists David Sterba
2016-05-11 12:47 ` [PATCH 11/17] btrfs: csum_tree_block: return proper errno value David Sterba
2016-05-11 12:47 ` [PATCH 12/17] btrfs: do not write corrupted metadata blocks to disk David Sterba
2016-05-11 12:47 ` [PATCH 13/17] Btrfs: fix invalid reference in replace_path David Sterba
2016-05-11 12:47 ` [PATCH 14/17] btrfs: handle non-fatal errors in btrfs_qgroup_inherit() David Sterba
2016-05-11 12:47 ` [PATCH 15/17] btrfs: fallback to vmalloc in btrfs_compare_tree David Sterba
2016-05-11 12:47 ` [PATCH 16/17] Btrfs: don't use src fd for printk David Sterba
2016-05-11 12:47 ` [PATCH 17/17] btrfs: Reset IO error counters before start of device replacing David Sterba
2016-05-17 1:12 ` Greg KH [this message]
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=20160517011212.GA4194@kroah.com \
--to=greg@kroah.com \
--cc=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).