Comment 5 for bug 791019

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,