All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.17-rc2
Date: Tue, 25 Jan 2022 16:36:59 +0100	[thread overview]
Message-ID: <cover.1643122662.git.dsterba@suse.com> (raw)

Hi,

several fixes for defragmentation that got broken in 5.16 after
refactoring and added subpage support. The observed bugs are excessive
IO or uninterruptible ioctl.

All stable material. Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 36c86a9e1be3b29f9f075a946df55dfe1d818019:

  btrfs: output more debug messages for uncommitted transaction (2022-01-07 14:18:27 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.17-rc1-tag

for you to fetch changes up to 27cdfde181bcacd226c230b2fd831f6f5b8c215f:

  btrfs: update writeback index when starting defrag (2022-01-24 18:16:28 +0100)

----------------------------------------------------------------
Filipe Manana (5):
      btrfs: fix too long loop when defragging a 1 byte file
      btrfs: allow defrag to be interruptible
      btrfs: fix deadlock when reserving space during defrag
      btrfs: add back missing dirty page rate limiting to defrag
      btrfs: update writeback index when starting defrag

Qu Wenruo (2):
      btrfs: defrag: fix wrong number of defragged sectors
      btrfs: defrag: properly update range->start for autodefrag

 fs/btrfs/ioctl.c | 84 ++++++++++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 75 insertions(+), 9 deletions(-)

             reply	other threads:[~2022-01-25 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 15:36 David Sterba [this message]
2022-01-25 16:31 ` [GIT PULL] Btrfs fixes for 5.17-rc2 pr-tracker-bot

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=cover.1643122662.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.