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.13-rc2
Date: Tue, 3 Dec 2024 17:44:40 +0100 [thread overview]
Message-ID: <cover.1733243359.git.dsterba@suse.com> (raw)
Hi,
first batch of regression and regular fixes. Please pull, thanks.
- add lockdep annotations for io_uring/encoded read integration, inode
lock is held when returning to userspace
- properly reflect experimental config option to sysfs
- handle NULL root in case the rescue mode accepts invalid/damaged tree
roots (rescue=ibadroot)
- regression fix of a deadlock between transaction and extent locks
- fix pending bio accounting bug in encoded read ioctl
- fix NOWAIT mode when checking references for NOCOW files
- fix use-after-free in a rb-tree cleanup in ref-verify debugging tool
----------------------------------------------------------------
The following changes since commit e82c936293aafb4f33b153c684c37291b3eed377:
btrfs: send: check for read-only send root under critical section (2024-11-11 14:34:23 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.13-rc1-tag
for you to fetch changes up to 22d2e48e318564f8c9b09faf03ecb4f03fb44dd5:
btrfs: fix lockdep warnings on io_uring encoded reads (2024-11-29 16:56:38 +0100)
----------------------------------------------------------------
Filipe Manana (4):
btrfs: fix deadlock between transaction commits and extent locks
btrfs: sysfs: advertise experimental features only if CONFIG_BTRFS_EXPERIMENTAL=y
btrfs: don't loop for nowait writes when checking for cross references
btrfs: ref-verify: fix use-after-free after invalid ref action
Johannes Thumshirn (1):
btrfs: fix use-after-free in btrfs_encoded_read_endio()
Lizhi Xu (1):
btrfs: add a sanity check for btrfs root in btrfs_search_slot()
Mark Harmstone (1):
btrfs: fix lockdep warnings on io_uring encoded reads
fs/btrfs/ctree.c | 6 +++++-
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/inode.c | 18 ++++++++++++++----
fs/btrfs/ioctl.c | 10 ++++++++++
fs/btrfs/locking.h | 10 ++++++++++
fs/btrfs/ref-verify.c | 1 +
fs/btrfs/sysfs.c | 4 ++--
7 files changed, 43 insertions(+), 8 deletions(-)
next reply other threads:[~2024-12-03 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 16:44 David Sterba [this message]
2024-12-03 19:05 ` [GIT PULL] Btrfs fixes for 6.13-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.1733243359.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