public inbox for linux-kernel@vger.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 6.8-rc6
Date: Wed, 21 Feb 2024 12:27:15 +0100	[thread overview]
Message-ID: <cover.1708514684.git.dsterba@suse.com> (raw)

Hi,

two more fixes. Please pull, thanks.

- fix a deadlock in fiemap, there was a big lock around the whole operation
  that can interfere with a page fault and mkwrite, reducing the lock
  scope can also speed up fiemap

- fix range condition for extent defragmentation which could lead to worse
  layout in some cases

----------------------------------------------------------------
The following changes since commit 2f6397e448e689adf57e6788c90f913abd7e1af8:

  btrfs: don't refill whole delayed refs block reserve when starting transaction (2024-02-13 18:39:09 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.8-rc5-tag

for you to fetch changes up to b0ad381fa7690244802aed119b478b4bdafc31dd:

  btrfs: fix deadlock with fiemap and extent locking (2024-02-19 11:20:00 +0100)

----------------------------------------------------------------
Josef Bacik (1):
      btrfs: fix deadlock with fiemap and extent locking

Qu Wenruo (1):
      btrfs: defrag: avoid unnecessary defrag caused by incorrect extent size

 fs/btrfs/defrag.c    |  2 +-
 fs/btrfs/extent_io.c | 62 ++++++++++++++++++++++++++++++++++++++--------------
 2 files changed, 46 insertions(+), 18 deletions(-)

             reply	other threads:[~2024-02-21 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 11:27 David Sterba [this message]
2024-02-21 17:17 ` [GIT PULL] Btrfs fixes for 6.8-rc6 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.1708514684.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox