[LU-7345] lockdep warning on dt_write_lock(env,parent,0) Created: 27/Oct/15 Updated: 18/Nov/15 Resolved: 18/Nov/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.8.0 |
| Fix Version/s: | Lustre 2.8.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Olaf Faaland | Assignee: | Dmitry Eremin (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | llnl, patch | ||
| Environment: |
TOSS 2.3-6 / 2.6.32-504.16.2.1chaos.ch5.3.x86_64.debug |
||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Upon mounting MDT, lockdep emits a warning: [ INFO: possible recursive locking detected ] but task is already holding lock: other info that might help us debug this: stack backtrace: I believe this occurs because __local_file_create() calls dt_write_lock(env, dto, 0) followed by dt_write_lock(env, parent, 0); since dto and parent are both dt_object, and no lock class was explicitly set, the class for the embedded locks are the same and based on the class it appears to be a recursive lock attempt. So, I believe the warning to be a false positive. The actual stack, appears to me to be: I'll submit a patch. It does make the symptom go away, but it would be good for someone to confirm my diagnosis. |
| Comments |
| Comment by Gerrit Updater [ 27/Oct/15 ] |
|
Olaf Faaland-LLNL (faaland1@llnl.gov) uploaded a new patch: http://review.whamcloud.com/16957 |
| Comment by Peter Jones [ 27/Oct/15 ] |
|
Dmitry Could you please review this patch? Thanks Peter |
| Comment by Gerrit Updater [ 15/Nov/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/16957/ |
| Comment by Joseph Gmitter (Inactive) [ 18/Nov/15 ] |
|
Landed for 2.8 |