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-rc7
Date: Wed, 4 Sep 2024 20:11:04 +0200 [thread overview]
Message-ID: <cover.1725472780.git.dsterba@suse.com> (raw)
Hi,
a few more fixes, for stable trees. Please pull, thanks.
- followup fix for direct io and fsync under some conditions, reported
by QEMU users
- fix a potential leak when disabling quotas while some extent tracking
work can still happen
- in zoned mode handle unexpected change of zone write pointer in
RAID1-like block groups, turn the zones to read-only
----------------------------------------------------------------
The following changes since commit ecb54277cb63c273e8d74272e5b9bfd80c2185d9:
btrfs: fix uninitialized return value from btrfs_reclaim_sweep() (2024-08-27 16:42:09 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.11-rc6-tag
for you to fetch changes up to cd9253c23aedd61eb5ff11f37a36247cd46faf86:
btrfs: fix race between direct IO write and fsync when using same fd (2024-09-03 20:29:55 +0200)
----------------------------------------------------------------
Fedor Pchelkin (1):
btrfs: qgroup: don't use extent changeset when not needed
Filipe Manana (1):
btrfs: fix race between direct IO write and fsync when using same fd
Naohiro Aota (1):
btrfs: zoned: handle broken write pointer on zones
fs/btrfs/ctree.h | 1 -
fs/btrfs/direct-io.c | 16 +++-------------
fs/btrfs/file.c | 9 +++++++--
fs/btrfs/qgroup.c | 3 +--
fs/btrfs/transaction.h | 6 ++++++
fs/btrfs/zoned.c | 30 +++++++++++++++++++++++++-----
6 files changed, 42 insertions(+), 23 deletions(-)
next reply other threads:[~2024-09-04 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 18:11 David Sterba [this message]
2024-09-04 18:57 ` [GIT PULL] Btrfs fixes for 6.11-rc7 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.1725472780.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