diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-01-13 23:13:39 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-01-13 23:13:39 +0100 |
| commit | f4b3e631b39db31f7375cce0b5e4111d14cde511 (patch) | |
| tree | 2dc8a21d0432bad2fe86c5a41cc24f972948025e /kernel/locking | |
| parent | Revert "kernfs: implement kernfs_{de|re}activate[_self]()" (diff) | |
| download | linux-f4b3e631b39db31f7375cce0b5e4111d14cde511.tar.xz linux-f4b3e631b39db31f7375cce0b5e4111d14cde511.zip | |
Revert "kernfs: make kernfs_get_active() block if the node is deactivated but not removed"
This reverts commit 895a068a524e134900b9d98b519309b7aae7bbb1.
Tejun writes:
I'm sorry but can you please revert the whole series?
get_active() waiting while a node is deactivated has potential
to lead to deadlock and that deactivate/reactivate interface is
something fundamentally flawed and that cgroup will have to work
with the remove_self() like everybody else. IOW, I think the
first posting was correct.
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/locking')
0 files changed, 0 insertions, 0 deletions