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.8-rc7
Date: Mon, 26 Feb 2024 17:49:20 +0100 [thread overview]
Message-ID: <cover.1708962398.git.dsterba@suse.com> (raw)
Hi,
a few more fixes for recently reported or discovered problems. Please
pull, thanks.
- fix corner case of send that would generate potentially large stream
of zeros if there's a hole at the end of the file
- fix chunk validation in zoned mode on conventional zones, it was
possible to create chunks that would not be allowed on sequential
zones
- fix validation of dev-replace ioctl filenames
- fix KCSAN warnings about access to block reserve struct members
----------------------------------------------------------------
The following changes since commit b0ad381fa7690244802aed119b478b4bdafc31dd:
btrfs: fix deadlock with fiemap and extent locking (2024-02-19 11:20:00 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.8-rc6-tag
for you to fetch changes up to c7bb26b847e5b97814f522686068c5628e2b3646:
btrfs: fix data race at btrfs_use_block_rsv() when accessing block reserve (2024-02-22 12:15:12 +0100)
----------------------------------------------------------------
David Sterba (1):
btrfs: dev-replace: properly validate device names
Filipe Manana (3):
btrfs: send: don't issue unnecessary zero writes for trailing hole
btrfs: fix data races when accessing the reserved amount of block reserves
btrfs: fix data race at btrfs_use_block_rsv() when accessing block reserve
Johannes Thumshirn (1):
btrfs: zoned: don't skip block group profile checks on conventional zones
fs/btrfs/block-rsv.c | 2 +-
fs/btrfs/block-rsv.h | 32 ++++++++++++++++++++++++++++++++
fs/btrfs/dev-replace.c | 24 ++++++++++++++++++++----
fs/btrfs/send.c | 17 +++++++++++++----
fs/btrfs/space-info.c | 26 +++++++++++++-------------
fs/btrfs/zoned.c | 9 +++++++++
6 files changed, 88 insertions(+), 22 deletions(-)
next reply other threads:[~2024-02-26 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 16:49 David Sterba [this message]
2024-02-26 19:29 ` [GIT PULL] Btrfs fixes for 6.8-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.1708962398.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