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.15-rc3
Date: Thu, 17 Apr 2025 11:49:55 +0200 [thread overview]
Message-ID: <cover.1744883021.git.dsterba@suse.com> (raw)
Hi,
please pull a few fixes, thanks.
- handle encoded read ioctl returning EAGAIN so it does not mistakenly
free the work structure
- escape subvolume path in mount option list so it cannot be wrongly
parsed when the path contains ","
- remove folio size assertions when writing super block to device with
enabled large folios
----------------------------------------------------------------
The following changes since commit 35fec1089ebb5617f85884d3fa6a699ce6337a75:
btrfs: zoned: fix zone finishing with missing devices (2025-03-18 20:35:57 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.15-rc2-tag
for you to fetch changes up to 65f2a3b2323edde7c5de3a44e67fec00873b4217:
btrfs: remove folio order ASSERT()s in super block writeback path (2025-04-01 01:02:42 +0200)
----------------------------------------------------------------
Johannes Kimmel (1):
btrfs: correctly escape subvol in btrfs_show_options()
Qu Wenruo (1):
btrfs: remove folio order ASSERT()s in super block writeback path
Sidong Yang (1):
btrfs: ioctl: don't free iov when btrfs_encoded_read() returns -EAGAIN
fs/btrfs/disk-io.c | 2 --
fs/btrfs/ioctl.c | 2 ++
fs/btrfs/super.c | 3 +--
3 files changed, 3 insertions(+), 4 deletions(-)
next reply other threads:[~2025-04-17 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 9:49 David Sterba [this message]
2025-04-17 17:06 ` [GIT PULL] Btrfs fixes for 6.15-rc3 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.1744883021.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