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 6.11-rc4, part 2
Date: Sun, 18 Aug 2024 14:43:54 +0200	[thread overview]
Message-ID: <cover.1723984416.git.dsterba@suse.com> (raw)

Hi,

a few more fixes. We got reports that shrinker added in 6.10 still
causes latency spikes and the fixes don't handle all corner cases. Due
to summer holidays we're taking a shortcut to disable it for release
builds and will fix it in the near future.

Please pull, thanks.

- only enable extent map shrinker for DEBUG builds, temporary quick fix
  to avoid latency spikes for regular builds

- update target inode's ctime on unlink, mandated by POSIX

- properly take lock to read/update block group's zoned variables

- add counted_by() annotations

----------------------------------------------------------------
The following changes since commit 6252690f7e1b173b86a4c27dfc046b351ab423e7:

  btrfs: fix invalid mapping of extent xarray state (2024-08-13 15:36:57 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.11-rc3-tag

for you to fetch changes up to 534f7eff9239c1b0af852fc33f5af2b62c00eddf:

  btrfs: only enable extent map shrinker for DEBUG builds (2024-08-16 21:22:39 +0200)

----------------------------------------------------------------
Jeff Layton (1):
      btrfs: update target inode's ctime on unlink

Naohiro Aota (1):
      btrfs: zoned: properly take lock to read/update block group's zoned variables

Qu Wenruo (2):
      btrfs: tree-checker: add dev extent item checks
      btrfs: only enable extent map shrinker for DEBUG builds

Thorsten Blum (1):
      btrfs: send: annotate struct name_cache_entry with __counted_by()

 fs/btrfs/free-space-cache.c | 14 +++++----
 fs/btrfs/inode.c            |  1 +
 fs/btrfs/send.c             |  2 +-
 fs/btrfs/super.c            |  8 +++++-
 fs/btrfs/tree-checker.c     | 69 +++++++++++++++++++++++++++++++++++++++++++++
 5 files changed, 86 insertions(+), 8 deletions(-)

             reply	other threads:[~2024-08-18 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 12:43 David Sterba [this message]
2024-08-18 17:23 ` [GIT PULL] Btrfs fixes for 6.11-rc4, part 2 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.1723984416.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.