diff options
author | Alex Elder <elder@inktank.com> | 2013-05-31 15:17:01 -0500 |
---|---|---|
committer | Sage Weil <sage@inktank.com> | 2013-07-03 15:32:42 -0700 |
commit | 1ba0f1e7975ad07557f7a931522bdcd813ae35f6 (patch) | |
tree | 9203d8f6b37c07e699194e981c5b3828f678252b /net/wireless/lib80211_crypt_wep.c | |
parent | 82a442d239695a242c4d584464c9606322cd02aa (diff) | |
download | talos-op-linux-1ba0f1e7975ad07557f7a931522bdcd813ae35f6.tar.gz talos-op-linux-1ba0f1e7975ad07557f7a931522bdcd813ae35f6.zip |
rbd: don't hold ctl_mutex to get/put device
When an rbd device is first getting mapped, its device registration
is protected the control mutex. There is no need to do that though,
because the device has already been assigned an id that's guaranteed
to be unique.
An unmap of an rbd device won't proceed if the device has a non-zero
open count or is already being unmapped. So there's no need to hold
the control mutex in that case either.
Finally, an rbd device can't be opened if it is being removed, and
it won't go away if there is a non-zero open count. So here too
there's no need to hold the control mutex while getting or putting a
reference to an rbd device's Linux device structure.
Drop the mutex calls in these cases.
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Diffstat (limited to 'net/wireless/lib80211_crypt_wep.c')
0 files changed, 0 insertions, 0 deletions