[LU-49] There is a race window between server obd cleanup and its handling of client connection Created: 21/Jan/11  Updated: 10/Apr/12  Resolved: 10/Apr/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 1.8.6
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Zhenyu Xu Assignee: Zhenyu Xu
Resolution: Cannot Reproduce Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 10491

 Description   

In class_cleanup() before the server obd's stopping flag is set, a new
client connection request can be handled in target_handle_connect();
after the target obd (server obd) is found, and before its refcount is
increased, class_cleanup() can be processed and run through
class_decref(); it find that the server obd's refcount becomes to 0;
at this point, target_handle_connect() can go on and add target obd
(server obd) refcount and create the client export.


Generated at Sat Feb 10 01:03:13 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.