All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: Please revert "btrfs: Honour FITRIM range constraints during free space trim" from all stable trees
Date: Wed, 29 May 2019 18:57:43 +0200	[thread overview]
Message-ID: <20190529165743.GA15290@suse.cz> (raw)
In-Reply-To: <20190529113300.GB11952@kroah.com>

On Wed, May 29, 2019 at 04:33:00AM -0700, Greg Kroah-Hartman wrote:
> On Wed, May 29, 2019 at 01:23:14PM +0200, David Sterba wrote:
> > Hi,
> > 
> > upon closer inspection we found a problem with the patch
> > 
> > "btrfs: Honour FITRIM range constraints during free space trim"
> > 
> > that has been merged to 5.1.4. This could happen with ranged FITRIM
> > where the range is not 'honoured' as it was supposed to.
> > 
> > Please revert it and push in the next stable release so the buggy
> > version is not in the wild for too long.
> > 
> > Affected trees:
> > 
> > 5.0.18
> > 5.1.4
> > 4.9.179
> > 4.19.45
> > 4.14.122
> > 
> > Master branch will have the revert too. Thanks.
> 
> What is the git commit id of the revert in Linus's tree?

Due to further changes in the code, a revert that will be in Linus'
branch can't be backported and stable-specific patches would have to be
provided anyway. There's a slight change in logic and handling of the
trimmed ranges, the upstream revert removes code and updates calls to
functions that are not in the stable branches.

So I'm going to send you patches for all the affected branches.

After analyzing the situation, the conclusion is that the patch should
have never been tagged for stable.  The patch is in 5.2-rc ie. an
unreleased kernel and the bug would be handled as a regression before
5.20 final.

The backport to stable happened before we knew that so the reverts are
IMO the best solution we have now. I hope you understand that and sorry
for the trouble.

  parent reply	other threads:[~2019-05-29 16:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 11:23 Please revert "btrfs: Honour FITRIM range constraints during free space trim" from all stable trees David Sterba
2019-05-29 11:33 ` Greg Kroah-Hartman
2019-05-29 11:57   ` David Sterba
2019-06-04  8:19     ` Greg Kroah-Hartman
2019-06-04 11:03       ` David Sterba
2019-06-04 11:34         ` Greg Kroah-Hartman
2019-06-12 11:06           ` David Sterba
2019-05-29 16:57   ` David Sterba [this message]
2019-05-29 18:36     ` Greg Kroah-Hartman
2019-05-29 17:25 ` [PATCH for 4.14.x] Revert "btrfs: Honour FITRIM range constraints during free space trim" David Sterba
2019-05-29 17:25 ` [PATCH for 4.19.x] " David Sterba
2019-05-29 17:25 ` [PATCH for 4.9.x] " David Sterba
2019-05-29 17:25 ` [PATCH for 5.0.x] " David Sterba
2019-05-29 17:25 ` [PATCH for 5.1.x] " David Sterba

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=20190529165743.GA15290@suse.cz \
    --to=dsterba@suse.cz \
    --cc=gregkh@linuxfoundation.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 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.