summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorDennis Zhou <dennis@kernel.org>2018-12-05 12:10:27 -0500
committerJens Axboe <axboe@kernel.dk>2018-12-07 22:26:36 -0700
commitb978962ad4f7f9c06e5aa07b2a9b22f6d600456c (patch)
tree2b32f74f61953f497e29cd1a90460bbd89e3296b /kernel
parent0fe061b9f03c27d0370888efc22d4b3ac7af90cf (diff)
downloadlinux-b978962ad4f7f9c06e5aa07b2a9b22f6d600456c.tar.gz
linux-b978962ad4f7f9c06e5aa07b2a9b22f6d600456c.tar.bz2
linux-b978962ad4f7f9c06e5aa07b2a9b22f6d600456c.zip
blkcg: update blkg_lookup_create() to do locking
To know when to create a blkg, the general pattern is to do a blkg_lookup() and if that fails, lock and do the lookup again, and if that fails finally create. It doesn't make much sense for everyone who wants to do creation to write this themselves. This changes blkg_lookup_create() to do locking and implement this pattern. The old blkg_lookup_create() is renamed to __blkg_lookup_create(). If a call site wants to do its own error handling or already owns the queue lock, they can use __blkg_lookup_create(). This will be used in upcoming patches. Signed-off-by: Dennis Zhou <dennis@kernel.org> Reviewed-by: Josef Bacik <josef@toxicpanda.com> Acked-by: Tejun Heo <tj@kernel.org> Reviewed-by: Liu Bo <bo.liu@linux.alibaba.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions