diff options
author | Jiang Biao <jiang.biao2@zte.com.cn> | 2018-04-18 08:37:18 -0600 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2018-04-18 08:37:18 -0600 |
commit | 946b81da114b8ba5c74bb01e57c0c6eca2bdc801 (patch) | |
tree | 5f4adb9a9a46eaee2c142dfc7f76d60abaea07da /scripts/cleanpatch | |
parent | 0ce9144471de9ee09306ca0127e7cd27521ccc3f (diff) | |
download | linux-946b81da114b8ba5c74bb01e57c0c6eca2bdc801.tar.bz2 |
blkcg: don't hold blkcg lock when deactivating policy
As described in the comment of blkcg_activate_policy(),
*Update of each blkg is protected by both queue and blkcg locks so
that holding either lock and testing blkcg_policy_enabled() is
always enough for dereferencing policy data.*
with queue lock held, there is no need to hold blkcg lock in
blkcg_deactivate_policy(). Similar case is in
blkcg_activate_policy(), which has removed holding of blkcg lock in
commit 4c55f4f9ad3001ac1fefdd8d8ca7641d18558e23.
Signed-off-by: Jiang Biao <jiang.biao2@zte.com.cn>
Signed-off-by: Wen Yang <wen.yang99@zte.com.cn>
CC: Tejun Heo <tj@kernel.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'scripts/cleanpatch')
0 files changed, 0 insertions, 0 deletions