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-rc5
Date: Tue, 15 Feb 2022 15:44:49 +0100	[thread overview]
Message-ID: <cover.1644935941.git.dsterba@suse.com> (raw)

Hi,

a few more fixups. Please pull, thanks.

* yield CPU more often when defragmenting a large file

* skip defragmenting extents already under writeback

* improve error message when send fails to write file data

* get rid of warning when mounted with flushoncommit

----------------------------------------------------------------
The following changes since commit 40cdc509877bacb438213b83c7541c5e24a1d9ec:

  btrfs: skip reserved bytes warning on unmount after log cleanup failure (2022-01-31 16:06:50 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 2e7be9db125a0bf940c5d65eb5c40d8700f738b5:

  btrfs: send: in case of IO error log it (2022-02-09 18:53:26 +0100)

----------------------------------------------------------------
Dāvis Mosāns (1):
      btrfs: send: in case of IO error log it

Filipe Manana (1):
      btrfs: get rid of warning on transaction commit when using flushoncommit

Qu Wenruo (2):
      btrfs: don't hold CPU for too long when defragging a file
      btrfs: defrag: don't try to defrag extents which are under writeback

 fs/btrfs/ioctl.c       |  5 +++++
 fs/btrfs/send.c        |  4 ++++
 fs/btrfs/transaction.c | 12 ++++++++++--
 3 files changed, 19 insertions(+), 2 deletions(-)

             reply	other threads:[~2022-02-15 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 14:44 David Sterba [this message]
2022-02-15 17:18 ` [GIT PULL] Btrfs fixes for 5.17-rc5 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.1644935941.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.