Skip to contentSkip to conversation

nvme: fix namespace removal list

PATCH In review Keith Busch 3 participants 3 messages Jun 13, 2024 – Jun 19, 2024 NVMe

lore
Share & tools
lore
#0 lore raw

PATCH v3 1/1 nvme: fix namespace removal list

From: Keith Busch <[email protected]>

This function wants to move a subset of a list from one element to the tail into another list. It also needs to use the srcu synchronize instead of the regular rcu version. Do this one element at a time because that's the only to do it.

Fixes be647e2c76b27f4 ("nvme: use srcu for iterating namespace list")

---
It would be neat to have a more elegant helper that we've been messing with, and be able to use a single srcu synchronize, but in the interest of time, this patch will fix the regression.

I was hoping to not have per-ns srcu sync's, but this path pretty much only gets called on the last namespace anyway, so it should functionally work out to be a single sync without to optimizations.

 drivers/nvme/host/core.c | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/nvme/host/core.c +5 -4
index c40930d10bd34..782090ce0bc10 100644
@@ -3960,12 +3960,13 @@ static void nvme_remove_invalid_namespaces(struct nvme_ctrl *ctrl,
 
 	mutex_lock(&ctrl->namespaces_lock);
 	list_for_each_entry_safe(ns, next, &ctrl->namespaces, list) {
-		if (ns->head->ns_id > nsid)
-			list_splice_init_rcu(&ns->list, &rm_list,
-					     synchronize_rcu);
+		if (ns->head->ns_id > nsid) {
+			list_del_rcu(&ns->list);
+			synchronize_srcu(&ctrl->srcu);
+			list_add_tail_rcu(&ns->list, &rm_list);
+		}
 	}
 	mutex_unlock(&ctrl->namespaces_lock);
-	synchronize_srcu(&ctrl->srcu);
 
 	list_for_each_entry_safe(ns, next, &rm_list, list)
 		nvme_ns_remove(ns);
Signature · 1 line
2.43.0
maintainer Reviewed-by on v3 1/1
#1 lore raw
Quoted 7 lines · Keith Busch

It would be neat to have a more elegant helper that we've been messing with, and be able to use a single srcu synchronize, but in the interest of time, this patch will fix the regression.

I was hoping to not have per-ns srcu sync's, but this path pretty much only gets called on the last namespace anyway, so it should functionally work out to be a single sync without to optimizations.

Yeah, compared to the 2-3 synchronize_srcu calls in nvme_ns_remove one more probably doesn't matter right now..

Looks good: