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 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html