Project

General

Profile

Actions

Bug #14753

closed

lokdep: uses lock name as the lock identity

Added by Yehuda Sadeh about 8 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

This is problematic if having multiple lock instances that share the same name.

Actions

Also available in: Atom PDF