On Sat, Mar 20, 2021 at 11:49:35PM -0700, Sagi Grimberg wrote:
quoted
Hmm. I don't think head->srcu is intended to protect the current path.
We also call nvme_mpath_clear_current_path from nvme_complete_rq or
nvme_ns_remove, which has no locking at all. The srcu protection is
for head->list, but leaks into the current path due to the __rcu
annotations.
OK, care to send a formal patch that I can give a test drive?
I'll write a changelog. But as-is this should be testable.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme