On Sun, Feb 09, 2020 at 10:59:50AM -0500, Sasha Levin wrote: > On Sun, Feb 09, 2020 at 02:26:40PM +0100, Greg KH wrote: > > On Sun, Feb 09, 2020 at 02:04:21PM +0100, Jiri Slaby wrote: > > > On 09. 02. 20, 12:33, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > > > > > The patch below does not apply to the 5.5-stable tree. > > > > If someone wants it applied there, or to any other stable or longterm > > > > tree, then please email the backport, including the original git commit > > > > id to <stable@xxxxxxxxxxxxxxx>. > > > > > > > > thanks, > > > > > > > > greg k-h > > > > > > > > ------------------ original commit in Linus's tree ------------------ > > > > > > > > From d55966c4279bfc6a0cf0b32bf13f5df228a1eeb6 Mon Sep 17 00:00:00 2001 > > > > From: Josef Bacik <josef@xxxxxxxxxxxxxx> > > > > Date: Fri, 31 Jan 2020 09:31:05 -0500 > > > > Subject: [PATCH] btrfs: do not zero f_bavail if we have available space > > > > > > 5.5.2 was already released with this patch: > > > commit 165387a9c90152f35976d82feca6eff5f0d5ac02 > > > Author: Josef Bacik <josef@xxxxxxxxxxxxxx> > > > Date: Fri Jan 31 09:31:05 2020 -0500 > > > > > > btrfs: do not zero f_bavail if we have available space > > > > > > commit d55966c4279bfc6a0cf0b32bf13f5df228a1eeb6 upstream. > > > > > > It cannot be applied twice :). > > > > Oops, Sasha beat me too it, sorry for the noise :) > > I've grabbed it for the fixes: tag, sorry :) Not a problem, much rather see patches try to get applied more than once, than not at all :)
