Hi Ritesh.
I guess, these would be the other kind of issues which might show up now, since powerpc is moved to CONFIG_PREEMPTION=y with lazy preempt as the default preemption mode. It will be nice to have some mechanism to catch these error handling paths where preempt counts might be getting leaked.
There is CONFIG_DEBUG_PREEMPT=y which helps you to catch these issue where count leak happens. Otherwise we only see end result, but not the culprit. That said, we do have issues of not nesting with get_cpu/put_cpu in few places and preempt_disable/preempt_enable in few return paths still.
