On 02/01/2016 04:28 AM, Peter Zijlstra wrote: > Its just the acct_account_cputime() callers that I suspect will all have > IRQs disabled, but it would still be goot to verify that with a > WARN_ON(!irqs_disabled()) test in there for at least one test run, and > then include that you did this in the Changelog.
I verified that the WARN_ON did not trigger, but I forgot to include that in the changelog for v4 -- All rights reversed
