From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.19-rc7
Date: Mon, 11 Jul 2022 23:16:19 +0200 [thread overview]
Message-ID: <cover.1657571742.git.dsterba@suse.com> (raw)
Hi,
a few more fixes that seem to me to be important enough to get merged
before release, described below. Please pull, thanks.
- in zoned mode, fix leak of a structure when reading zone info, this
happens on normal path so this can be significant
- in zoned mode, revert an optimization added in 5.19-rc1 to finish a
zone when the capacity is full, but this is not reliable in all cases
- try to avoid short reads for compressed data or inline files when it's
a NOWAIT read, applications should handle that but there are two,
qemu and mariadb, that are affected
----------------------------------------------------------------
The following changes since commit 037e127452b973f45b34c1e88a1af183e652e657:
Documentation: update btrfs list of features and link to readthedocs.io (2022-06-21 14:47:19 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.19-rc6-tag
for you to fetch changes up to b3a3b0255797e1d395253366ba24a4cc6c8bdf9c:
btrfs: zoned: drop optimization of zone finish (2022-07-08 19:18:00 +0200)
----------------------------------------------------------------
Christoph Hellwig (1):
btrfs: zoned: fix a leaked bioc in read_zone_info
Filipe Manana (1):
btrfs: return -EAGAIN for NOWAIT dio reads/writes on compressed and inline extents
Naohiro Aota (1):
btrfs: zoned: drop optimization of zone finish
fs/btrfs/inode.c | 14 +++++++++++++-
fs/btrfs/zoned.c | 34 ++++++++++++++--------------------
2 files changed, 27 insertions(+), 21 deletions(-)
next reply other threads:[~2022-07-11 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 21:16 David Sterba [this message]
2022-07-11 21:44 ` [GIT PULL] Btrfs fixes for 5.19-rc7 pr-tracker-bot
2022-07-16 14:06 David Sterba
2022-07-16 15:34 ` Matthew Wilcox
2022-07-21 14:45 ` David Sterba
2022-07-21 15:43 ` David Sterba
2022-07-16 22:10 ` 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.1657571742.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;
as well as URLs for NNTP newsgroup(s).