All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolay Borisov <nborisov@suse.com>
Cc: stable@vger.kernel.org, dsterba@suse.cz, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH] btrfs: Honour FITRIM range constraints during free space trim
Date: Thu, 23 May 2019 19:58:26 +0200	[thread overview]
Message-ID: <20190523175826.GH29438@kroah.com> (raw)
In-Reply-To: <20190520135138.5594-1-nborisov@suse.com>

On Mon, May 20, 2019 at 04:51:38PM +0300, Nikolay Borisov wrote:
> Up until now trimming the freespace was done irrespective of what the
> arguments of the FITRIM ioctl were. For example fstrim's -o/-l arguments
> will be entirely ignored. Fix it by correctly handling those paramter.
> This requires breaking if the found freespace extent is after the end of
> the passed range as well as completing trim after trimming
> fstrim_range::len bytes.
> 
> Fixes: 499f377f49f0 ("btrfs: iterate over unused chunk space in FITRIM")
> CC: stable@vger.kernel.org # 4.4+
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> Reviewed-by: David Sterba <dsterba@suse.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> 
> Hello, 
> 
> Here is a backport of upstream commit c2d1b3aae33605a61cbab445d8ae1c708ccd2698
> for 4.14.y. Please apply 
>  fs/btrfs/extent-tree.c | 25 +++++++++++++++++++------
>  1 file changed, 19 insertions(+), 6 deletions(-)

All of these now queued up, thanks.

greg k-h

  reply	other threads:[~2019-05-23 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 13:51 [PATCH] btrfs: Honour FITRIM range constraints during free space trim Nikolay Borisov
2019-05-23 17:58 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-20 13:52 Nikolay Borisov
2019-05-20 13:54 Nikolay Borisov

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=20190523175826.GH29438@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=nborisov@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.