stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: stable@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>, linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Btrfs stable updates for 4.0
Date: Thu, 11 Jun 2015 18:06:32 +0200	[thread overview]
Message-ID: <cover.1434037853.git.dsterba@suse.cz> (raw)

Hi,

please queue the following patches to 4.0 stable. There are fixes for user
visible bugs and one usability regression with RAID1 -> single conversion
during balance.

One of the patches does not apply cleanly to 4.0.5, there's a minor conflict in
patch context (153c35b6cccc0c72de9fae06c8e2c8b2c47d79d4, the last one). A reply
to this mail is the adapted version or you can pull/cherry-pick from

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-stable-4.0

Subjects:
	Btrfs: send, add missing check for dead clone root
	Btrfs: send, don't leave without decrementing clone root's send_progress
	btrfs: incorrect handling for fiemap_fill_next_extent return
	btrfs: cleanup orphans while looking up default subvolume
	Btrfs: fix range cloning when same inode used as source and destination
	Btrfs: fix uninit variable in clone ioctl
	Btrfs: fix regression in raid level conversion
Commits:
	5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+
	2f1f465ae6da244099af55c066e5355abd8ff620 # 3.14+
	26e726afe01c1c82072cf23a5ed89ce25f39d9f2 # 3.10+
	727b9784b6085c99c2f836bf4fcc2848dc9cf904 # 3.14+
	df858e76723ace61342b118aa4302bd09de4e386 # 4.0+
	de249e66a73d696666281cd812087979c6fae552 # 4.0+
	153c35b6cccc0c72de9fae06c8e2c8b2c47d79d4 # 4.0+

Thanks.

             reply	other threads:[~2015-06-11 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 16:06 David Sterba [this message]
2015-06-11 16:06 ` [PATCH 7/7] Btrfs: fix regression in raid level conversion David Sterba
2015-06-17 14:47 ` Btrfs stable updates for 4.0 Luis Henriques
2015-06-19 20:31 ` Greg KH
2015-06-25 15:10   ` David Sterba
2015-06-25 15:59     ` Greg KH
2015-06-19 20:32 ` 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=cover.1434037853.git.dsterba@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --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 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).