diff options
author | Christoph Lameter <cl@linux.com> | 2012-01-17 10:27:31 -0500 |
---|---|---|
committer | Luis Henriques <luis.henriques@canonical.com> | 2012-04-05 11:17:32 -0400 |
commit | b9b217b90f9d9062c031ea5fabacbda8c43348eb (patch) | |
tree | 9d87e949d11ddebad0a21a6f4abda96401e4c780 /kernel/module.c | |
parent | e57ce09d66a6f1fe76cb89335cb2a65c11b097d5 (diff) |
slub: Do not hold slub_lock when calling sysfs_slab_add()
BugLink: http://bugs.launchpad.net/bugs/971808
commit 66c4c35c6bc5a1a452b024cf0364635b28fd94e4 upstream.
sysfs_slab_add() calls various sysfs functions that actually may
end up in userspace doing all sorts of things.
Release the slub_lock after adding the kmem_cache structure to the list.
At that point the address of the kmem_cache is not known so we are
guaranteed exlusive access to the following modifications to the
kmem_cache structure.
If the sysfs_slab_add fails then reacquire the slub_lock to
remove the kmem_cache structure from the list.
Reported-by: Sasha Levin <levinsasha928@gmail.com>
Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
Signed-off-by: Christoph Lameter <cl@linux.com>
Signed-off-by: Pekka Enberg <penberg@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/module.c')
0 files changed, 0 insertions, 0 deletions