+++ This bug was initially created as a clone of Bug #1444125 +++
panic is in the attachment
Could you give me some help to verify this bug since I have no idea how to reproduce this bug?
@zhaozhanqi: Sadly, I can't tell you how to verify this fix. It happens rarely, and was only seen in the logs on a busy, long-running system. It would be a tricky race-condition to manage to trigger. The best we can do is test that it doesn't break anything else, and that the code review caught all of the places the lock was needed.
Definitely run the idling and unidling test cases since that will be where the code is exercised.
Do regression testing on 126.96.36.199 include parallel idling/unidling operations.
No regression issue found and no panic error found in the logs.
Move the bug to verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.