From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: some misc cleanups and a fix around page reading
Date: Thu, 3 Feb 2022 15:36:41 +0000 [thread overview]
Message-ID: <cover.1643902108.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
A small set of changes, mostly cleanups, a fix for an error that is not
being returned, and adding a couple lockdep assertions.
Filipe Manana (4):
btrfs: stop checking for NULL return from btrfs_get_extent()
btrfs: fix lost error return value when reading a data page
btrfs: remove no longer used counter when reading data page
btrfs: assert we have a write lock when removing and replacing extent
maps
fs/btrfs/extent_io.c | 12 +++++-------
fs/btrfs/extent_map.c | 4 ++++
fs/btrfs/inode.c | 9 +++++++--
fs/btrfs/tests/extent-map-tests.c | 2 ++
4 files changed, 18 insertions(+), 9 deletions(-)
--
2.33.0
next reply other threads:[~2022-02-03 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 15:36 fdmanana [this message]
2022-02-03 15:36 ` [PATCH 1/4] btrfs: stop checking for NULL return from btrfs_get_extent() fdmanana
2022-02-04 8:19 ` Johannes Thumshirn
2022-02-04 11:17 ` Filipe Manana
2022-02-03 15:36 ` [PATCH 2/4] btrfs: fix lost error return value when reading a data page fdmanana
2022-02-03 15:36 ` [PATCH 3/4] btrfs: remove no longer used counter when reading " fdmanana
2022-02-03 15:36 ` [PATCH 4/4] btrfs: assert we have a write lock when removing and replacing extent maps fdmanana
2022-02-04 8:25 ` [PATCH 0/4] btrfs: some misc cleanups and a fix around page reading Johannes Thumshirn
2022-02-04 16:35 ` David Sterba
2022-02-08 15:45 ` David Sterba
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.1643902108.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.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