diff options
author | Tejun Heo <tj@kernel.org> | 2013-06-12 20:52:35 -0700 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2013-06-13 11:08:27 -0700 |
commit | bc497bd33b2d6a6f07bc8574b4764edbd7fdffa8 (patch) | |
tree | 2425880399cae042dcb7bf9c4fefdbdaf67f6ab5 /lib/find_next_bit.c | |
parent | acac7883ee7bcc32476963bce7baf73d44574dd1 (diff) | |
download | op-kernel-dev-bc497bd33b2d6a6f07bc8574b4764edbd7fdffa8.zip op-kernel-dev-bc497bd33b2d6a6f07bc8574b4764edbd7fdffa8.tar.gz |
percpu-refcount: implement percpu_ref_cancel_init()
Normally, percpu_ref_init() initializes and percpu_ref_kill()
initiates destruction which completes asynchronously. The
asynchronous destruction can be problematic in init failure path where
the caller wants to destroy half-constructed object - distinguishing
half-constructed objects from the usual release method can be painful
for complex objects.
This patch implements percpu_ref_cancel_init() which synchronously
destroys the percpu_ref without invoking release. To avoid
unintentional misuses, the function requires the ref to have finished
percpu_ref_init() but never used and triggers WARN otherwise.
v2: Explain the weird name and usage restriction in the function
comment.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Kent Overstreet <koverstreet@google.com>
Diffstat (limited to 'lib/find_next_bit.c')
0 files changed, 0 insertions, 0 deletions