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-rc5
Date: Sun, 29 Dec 2024 08:40:38 +0100 [thread overview]
Message-ID: <cover.1735454878.git.dsterba@suse.com> (raw)
Hi,
a few more fixes that accumulated over the last two weeks, fixing some
user reported problems. Please pull, thanks.
- swapfile fixes
- conditional reschedule in the activation loop
- fix race with memory mapped file when activating
- make activation loop interruptible
- rework and fix extent sharing checks
- folio fixes
- in send, recheck folio mapping after unlock
- in relocation, recheck folio mapping after unlock
- fix waiting for encoded read io_uring requests
- fix transaction atomicity when enabling simple quotas
- move COW block trace point before the block gets freed
- print various sizes in sysfs with correct endianity
----------------------------------------------------------------
The following changes since commit f10bef73fb355e3fc85e63a50386798be68ff486:
btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (2024-12-06 15:04:18 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.13-rc4-tag
for you to fetch changes up to fca432e73db2bec0fdbfbf6d98d3ebcd5388a977:
btrfs: sysfs: fix direct super block member reads (2024-12-23 22:06:44 +0100)
----------------------------------------------------------------
Boris Burkov (2):
btrfs: check folio mapping after unlock in relocate_one_folio()
btrfs: check folio mapping after unlock in put_file_data()
Filipe Manana (5):
btrfs: fix use-after-free when COWing tree bock and tracing is enabled
btrfs: fix race with memory mapped writes when activating swap file
btrfs: fix swap file activation failure due to extents that used to be shared
btrfs: allow swap activation to be interruptible
btrfs: avoid monopolizing a core when activating a swap file
Johannes Thumshirn (1):
btrfs: fix use-after-free waiting for encoded read endios
Julian Sun (1):
btrfs: fix transaction atomicity bug when enabling simple quotas
Qu Wenruo (1):
btrfs: sysfs: fix direct super block member reads
fs/btrfs/ctree.c | 11 ++--
fs/btrfs/inode.c | 154 +++++++++++++++++++++++++++++++++++---------------
fs/btrfs/qgroup.c | 3 +-
fs/btrfs/relocation.c | 6 ++
fs/btrfs/send.c | 6 ++
fs/btrfs/sysfs.c | 6 +-
6 files changed, 130 insertions(+), 56 deletions(-)
next reply other threads:[~2024-12-29 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 7:40 David Sterba [this message]
2024-12-29 17:41 ` [GIT PULL] Btrfs fixes for 6.13-rc5 Linus Torvalds
2024-12-30 18:35 ` Konstantin Ryabitsev
2025-01-02 12:49 ` David Sterba
2024-12-29 18:22 ` 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.1735454878.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