On Fri, 3 Jun 2022, Rongwei Wang wrote: > Recently, I am also find other ways to solve this. That case was provided by > Muchun is useful (Thanks Muchun!). Indeed, it seems that use n->list_lock here > is unwise. Actually, I'm not sure if you recognize the existence of such race? > If all agrees this race, then the next question may be: do we want to solve > this problem? or as David said, it would be better to deprecate validate > attribute directly. I have no idea about it, hope to rely on your experience. > > In fact, I mainly want to collect your views on whether or how to fix this bug > here. Thanks! Well validate_slab() is rarely used and should not cause the hot paths to incur performance penalties. Fix it in the validation logic somehow? Or document the issue and warn that validation may not be correct if there are current operations on the slab being validated.
