On Fri, 4 Aug 2017, Laura Abbott wrote: > All slub debug features currently disable the fast path completely. > Some features such as consistency checks require this to allow taking of > locks. Poisoning and red zoning don't require this and can safely use > the per-cpu fast path. Introduce a Kconfig to continue to use the fast > path when 'fast' debugging options are enabled. The code will > automatically revert to always using the slow path when 'slow' options > are enabled.
Ok I see that the objects are initialized with poisoning and redzoning but I do not see that there is fastpath code to actually check the values before the object is reinitialized. Is that intentional or am I missing something?