From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/2] btrfs: fixes related to btrfs_folio_start_writer_lock()
Date: Wed, 9 Oct 2024 09:37:02 +1030 [thread overview]
Message-ID: <cover.1728428503.git.wqu@suse.com> (raw)
[Changelog]
v2:
- Remove the unused btrfs_folio_start_writer_lock()
v3:
- Split out the btrfs_folio_start_writer_lock() removal
As the initial fix needs to go backported to 5.15+, keeps the
modification as small as possible
The function lacks the proper folio->mapping check, thus we can even get
a folio not belonging to btrfs, and cause unexpeceted folio->private
updates.
Fix the only caller of btrfs_folio_start_writer_lock() inside
lock_delalloc_folios() and other sector size < page size handling of
lock_delalloc_folios().
Then finally remove btrfs_folio_start_writer_lock()
Qu Wenruo (2):
btrfs: fix the delalloc range locking if sector size < page size
btrfs: remove unused btrfs_folio_start_writer_lock()
fs/btrfs/extent_io.c | 17 ++++++++--------
fs/btrfs/subpage.c | 47 --------------------------------------------
fs/btrfs/subpage.h | 2 --
3 files changed, 9 insertions(+), 57 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-08 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 23:07 Qu Wenruo [this message]
2024-10-08 23:07 ` [PATCH v3 1/2] btrfs: fix the delalloc range locking if sector size < page size Qu Wenruo
2024-10-08 23:07 ` [PATCH v3 2/2] btrfs: remove unused btrfs_folio_start_writer_lock() Qu Wenruo
2024-10-16 15:16 ` [PATCH v3 0/2] btrfs: fixes related to btrfs_folio_start_writer_lock() 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.1728428503.git.wqu@suse.com \
--to=wqu@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.