From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH v2 0/2] Device name and RCU string
Date: Wed, 25 Jun 2025 15:37:15 +0200 [thread overview]
Message-ID: <cover.1750858539.git.dsterba@suse.com> (raw)
v2:
- drop patch adding RCU protection around update_dev_time(), there's a
sleeping allocation inside; after revisiting the RCU requirements, I
don't think it's needed and we can access the raw string (the same way
it was done with rcu_string), the time update is called from scratch
superblocks and after the ->dev_list hook is removed, so there's no
chance it can be reached from device_list_add
After recent simplifications of the RCU usage in messages, this patchset
implements the RCU protection directly without the RCU string so this
API can be removed completely as we don't have nor plan anything else to
use it for.
David Sterba (2):
btrfs: open code RCU for device name
btrfs: remove struct rcu_string
fs/btrfs/rcu-string.h | 40 ----------------------------------------
fs/btrfs/volumes.c | 29 +++++++++++++++++------------
fs/btrfs/volumes.h | 6 +++---
fs/btrfs/zoned.c | 23 +++++++++++------------
4 files changed, 31 insertions(+), 67 deletions(-)
delete mode 100644 fs/btrfs/rcu-string.h
--
2.49.0
next reply other threads:[~2025-06-25 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 13:37 David Sterba [this message]
2025-06-25 13:37 ` [PATCH v2 1/2] btrfs: open code RCU for device name David Sterba
2025-06-30 2:24 ` Wang Yugui
2025-06-30 16:21 ` David Sterba
2025-06-30 16:43 ` David Sterba
2025-06-30 17:07 ` Alan Huang
2025-07-01 14:47 ` David Sterba
2025-07-01 23:29 ` Wang Yugui
2025-07-04 3:14 ` David Sterba
2025-07-07 14:28 ` David Sterba
2025-06-25 13:37 ` [PATCH v2 2/2] btrfs: remove struct rcu_string David Sterba
2025-06-26 14:46 ` [PATCH v2 0/2] Device name and RCU string Daniel Vacek
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.1750858539.git.dsterba@suse.com \
--to=dsterba@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 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).