From: Greg KH <greg@kroah.com>
To: David Sterba <dsterba@suse.com>
Cc: stable@vger.kernel.org, clm@fb.com
Subject: Re: Btrfs patches for stable 4.8.x
Date: Tue, 3 Jan 2017 20:20:49 +0100 [thread overview]
Message-ID: <20170103192049.GA10478@kroah.com> (raw)
In-Reply-To: <20161214094953.16273-1-dsterba@suse.com>
On Wed, Dec 14, 2016 at 10:49:53AM +0100, David Sterba wrote:
> Hi,
>
> please apply the following patches to 4.8 series. There are fixes for user
> reported problems with device deletion and hung umount, plus other stability
> fixes. The commits apply cleanly to 4.8.14. Thanks.
>
> Commits:
>
> 9eb4a4a60b0e86a26f84cb5ac8f9493de6c3b1bb
> 20411dafe87a8cc8bcea9fe6d8d2791606222520
> 5f22e00270766e60be218a523acb1d9321abdafd
> f8ddb1eca6815a77c5b4e0bc6f7eedd6a5cf52fd
> bdce4057370d8e30b73ddef4721d97edb41c5390
> 2be8911a7849a459f092b8acb9f428fb8c779a0c
> eec7f79b72caad9cd1b051d18e02414653d50885
> 0a28de62d44e8b9d1bd19fa84ef04e954da1b5d9
> 9f7916b88b64ad2b8aef4758409dc6981de138cc
> 029484589cbcc9c86d604b31603edf84fd90bf80
>
> Subjects:
>
> * Btrfs: fix memory leak in reading btree blocks
> * Btrfs: bail out if block group has different mixed flag
> * Btrfs: return gracefully from balance if fs tree is
> * Btrfs: don't leak reloc root nodes on error
> * btrfs: clean the old superblocks before freeing the
> * Btrfs: fix memory leak in do_walk_down
> * btrfs: fix a possible umount deadlock
> * Btrfs: don't BUG() during drop snapshot
> * Btrfs: fix incremental send failure caused by balance
> * btrfs: make file clone aware of fatal signals
Should any of these also go to 4.4-stable?
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-03 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 9:49 Btrfs patches for stable 4.8.x David Sterba
2017-01-03 19:20 ` Greg KH [this message]
2017-01-03 19:22 ` Greg KH
2017-01-04 8:39 ` David Sterba
2017-01-04 9:38 ` 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=20170103192049.GA10478@kroah.com \
--to=greg@kroah.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--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.