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
Date: Thu, 15 Aug 2024 02:38:02 +0200 [thread overview]
Message-ID: <cover.1723673272.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch, with stable fixes and one regression
fix. Thanks.
- extend tree-checker verification of directory item type
- fix regression in page/folio and extent state tracking in xarray, the
dirty status can get out of sync and can cause problems e.g. a hang
- in send, detect last extent and allow to clone it instead of sending
it as write, reduces amount of data transferred in the stream
- fix checking extent references when cleaning deleted subvolumes
- fix one more case in the extent map shrinker, let it run only in the
kswapd context so it does not cause latency spikes during other
operations
----------------------------------------------------------------
The following changes since commit 7c626ce4bae1ac14f60076d00eafe71af30450ba:
Linux 6.11-rc3 (2024-08-11 14:27:14 -0700)
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 6252690f7e1b173b86a4c27dfc046b351ab423e7:
btrfs: fix invalid mapping of extent xarray state (2024-08-13 15:36:57 +0200)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: only run the extent map shrinker from kswapd tasks
btrfs: send: allow cloning non-aligned extent if it ends at i_size
Josef Bacik (1):
btrfs: check delayed refs when we're checking if a ref exists
Naohiro Aota (1):
btrfs: fix invalid mapping of extent xarray state
Qu Wenruo (1):
btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type
fs/btrfs/delayed-ref.c | 67 +++++++++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/delayed-ref.h | 2 ++
fs/btrfs/extent-tree.c | 51 ++++++++++++++++++++++++++++++++-----
fs/btrfs/extent_io.c | 14 +++++------
fs/btrfs/extent_map.c | 22 +++++-----------
fs/btrfs/send.c | 52 ++++++++++++++++++++++++++++----------
fs/btrfs/super.c | 10 ++++++++
fs/btrfs/tree-checker.c | 5 ++--
8 files changed, 179 insertions(+), 44 deletions(-)
next reply other threads:[~2024-08-15 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 0:38 David Sterba [this message]
2024-08-15 1:17 ` [GIT PULL] Btrfs fixes for 6.11-rc4 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.1723673272.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