Now security_task_free is called from __put_task_struct in ubuntu kernel, and __put_task_struct c can surely be called in softirq context. In upstream, there are no security_task_free at all.
If not calling security_task_free, where is it called from? Seems depending on security implementation, also more difficult fix will be involved than *_bh fix. Any way, using spin_[un]lock_bh is a easy fix, and no obvious performance degrade is introduced. I don't know security well, so let your guys decide how to fix this, :-) thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791019 Title: yama_ptracer_del lockdep warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
