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.1-rc2
Date: Tue, 18 Oct 2022 13:43:44 +0200 [thread overview]
Message-ID: <cover.1666091548.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes, thanks.
- fiemap fixes:
- add missing path cache update
- fix processing of delayed data and tree refs during backref walking,
this could lead to reporting incorrect extent sharing
- fix extent range locking under heavy contention to avoid deadlocks
- make it possible to test send v3 in debugging mode
- update links in MAINTAINERS
----------------------------------------------------------------
The following changes since commit cbddcc4fa3443fe8cfb2ff8e210deb1f6a0eea38:
btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer (2022-09-29 17:08:31 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.1-rc1-tag
for you to fetch changes up to 4efb365a3f04d0bee7833f168b0b00a15edefeac:
MAINTAINERS: update btrfs website links and files (2022-10-14 13:54:21 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: send: allow protocol version 3 with CONFIG_BTRFS_DEBUG
David Sterba (3):
btrfs: send: update command for protocol version check
btrfs: delete stale comments after merge conflict resolution
MAINTAINERS: update btrfs website links and files
Filipe Manana (4):
btrfs: add missing path cache update during fiemap
btrfs: fix processing of delayed data refs during backref walking
btrfs: fix processing of delayed tree block refs during backref walking
btrfs: ignore fiemap path cache if we have multiple leaves for a data extent
Josef Bacik (1):
btrfs: unlock locked extent area if we have contention
MAINTAINERS | 6 ++--
fs/btrfs/backref.c | 84 ++++++++++++++++++++++++++++++++++++++---------
fs/btrfs/backref.h | 1 +
fs/btrfs/block-group.c | 2 --
fs/btrfs/extent-io-tree.c | 15 +++++----
fs/btrfs/send.c | 5 ++-
fs/btrfs/send.h | 5 +++
7 files changed, 91 insertions(+), 27 deletions(-)
next reply other threads:[~2022-10-18 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 11:43 David Sterba [this message]
2022-10-18 19:06 ` [GIT PULL] Btrfs fixes for 6.1-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.1666091548.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.