From: Hannes Reinecke <hare@suse.de>
To: Daniel Wagner <dwagner@suse.de>, James Smart <james.smart@broadcom.com>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 12/12] nvmet-fc: use RCU list iterator for assoc_list
Date: Tue, 6 Feb 2024 14:51:24 +0900 [thread overview]
Message-ID: <b19e0b0f-6b1c-4126-931b-d7b0d01fb3da@suse.de> (raw)
In-Reply-To: <20240131085112.21668-13-dwagner@suse.de>
On 1/31/24 16:51, Daniel Wagner wrote:
> The assoc_list is a RCU protected list, thus use the RCU flavor of list
> functions.
>
> Let's use this opportunity and refactor this code and move the lookup
> into a helper and give it a descriptive name.
>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
> drivers/nvme/target/fc.c | 34 ++++++++++++++++++++++------------
> 1 file changed, 22 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/nvme/target/fc.c b/drivers/nvme/target/fc.c
> index 671d096745a5..fd229f310c93 100644
> --- a/drivers/nvme/target/fc.c
> +++ b/drivers/nvme/target/fc.c
> @@ -1114,14 +1114,27 @@ nvmet_fc_schedule_delete_assoc(struct nvmet_fc_tgt_assoc *assoc)
> queue_work(nvmet_wq, &assoc->del_work);
> }
>
> +static bool
> +nvmet_fc_assoc_exits(struct nvmet_fc_tgtport *tgtport, u64 association_id)
> +{
> + struct nvmet_fc_tgt_assoc *a;
> +
> + list_for_each_entry_rcu(a, &tgtport->assoc_list, a_list) {
> + if (association_id == a->association_id)
> + return true;
> + }
> +
> + return false;
> +}
> +
> static struct nvmet_fc_tgt_assoc *
> nvmet_fc_alloc_target_assoc(struct nvmet_fc_tgtport *tgtport, void *hosthandle)
> {
> - struct nvmet_fc_tgt_assoc *assoc, *tmpassoc;
> + struct nvmet_fc_tgt_assoc *assoc;
> unsigned long flags;
> + bool done;
> u64 ran;
> int idx;
> - bool needrandom = true;
>
> if (!tgtport->pe)
> return NULL;
> @@ -1145,24 +1158,21 @@ nvmet_fc_alloc_target_assoc(struct nvmet_fc_tgtport *tgtport, void *hosthandle)
> INIT_WORK(&assoc->del_work, nvmet_fc_delete_assoc_work);
> atomic_set(&assoc->terminating, 0);
>
> - while (needrandom) {
> + done = false;
> + do {
> get_random_bytes(&ran, sizeof(ran) - BYTES_FOR_QID);
> ran = ran << BYTES_FOR_QID_SHIFT;
>
> spin_lock_irqsave(&tgtport->lock, flags);
> - needrandom = false;
> - list_for_each_entry(tmpassoc, &tgtport->assoc_list, a_list) {
> - if (ran == tmpassoc->association_id) {
> - needrandom = true;
> - break;
> - }
> - }
> - if (!needrandom) {
> + rcu_read_lock();
> + if (!nvmet_fc_assoc_exits(tgtport, ran)) {
> assoc->association_id = ran;
> list_add_tail_rcu(&assoc->a_list, &tgtport->assoc_list);
> + done = true;
> }
> + rcu_read_unlock();
> spin_unlock_irqrestore(&tgtport->lock, flags);
Odd. You already take the tgtport lock, so there really is no point in
using rcu_read_lock() here.
Or does the tgtport lock not protect the assoc_list?
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Ivo Totev, Andrew McDonald,
Werner Knoblich
next prev parent reply other threads:[~2024-02-06 5:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 8:51 [PATCH v5 00/12] enable nvmet-fc for blktests Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 01/12] nvme-fc: do not wait in vain when unloading module Daniel Wagner
2024-02-01 12:41 ` Hannes Reinecke
2024-01-31 8:51 ` [PATCH v5 02/12] nvmet-fcloop: swap the list_add_tail arguments Daniel Wagner
2024-02-01 12:42 ` Hannes Reinecke
2024-01-31 8:51 ` [PATCH v5 03/12] nvmet-fc: release reference on target port Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 04/12] nvmet-fc: defer cleanup using RCU properly Daniel Wagner
2024-02-01 12:43 ` Hannes Reinecke
2024-01-31 8:51 ` [PATCH v5 05/12] nvmet-fc: free queue and assoc directly Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 06/12] nvmet-fc: hold reference on hostport match Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 07/12] nvmet-fc: remove null hostport pointer check Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 08/12] nvmet-fc: do not tack refs on tgtports from assoc Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 09/12] nvmet-fc: abort command when there is no binding Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 10/12] nvmet-fc: avoid deadlock on delete association path Daniel Wagner
2024-02-06 3:03 ` Hannes Reinecke
2024-01-31 8:51 ` [PATCH v5 11/12] nvmet-fc: take ref count on tgtport before delete assoc Daniel Wagner
2024-01-31 8:51 ` [PATCH v5 12/12] nvmet-fc: use RCU list iterator for assoc_list Daniel Wagner
2024-01-31 17:31 ` Christoph Hellwig
2024-02-06 5:51 ` Hannes Reinecke [this message]
2024-02-06 19:22 ` Keith Busch
2024-02-12 10:31 ` Daniel Wagner
2024-02-01 0:28 ` [PATCH v5 00/12] enable nvmet-fc for blktests Keith Busch
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=b19e0b0f-6b1c-4126-931b-d7b0d01fb3da@suse.de \
--to=hare@suse.de \
--cc=dwagner@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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
all inboxes | Powered by JetHome®