padata_get_next needs to check whether the next object that
need serialization must be parallel processed by the local cpu.
This check was wrong implemented and returned always true,
so the try_again loop in padata_reorder was never taken. This
can lead to object leaks in some rare cases due to a
yield was used to wait until all references of the internal control
structure in use are dropped before it is freed. This patch implements
padata_flush_queues which actively flushes the padata percpu queues
in this case.
Signed-off-by: Steffen Klassert steffen.klass...@secunet.com
---
Signed-off-by: Steffen Klassert steffen.klass...@secunet.com
---
include/linux/padata.h | 53
kernel/padata.c| 50 +++-
2 files changed, 101 insertions(+), 2 deletions(-)
diff --git
Hi,
Herbert Xu wrote:
On Thu, Mar 18, 2010 at 10:24:41PM +0100, michael-...@fami-braun.de wrote:
Pekka Enberg schrieb:
Even with CONFIG_DEBUG_SLAB enabled or with CONFIG_SLUB and
CONFIG_SLUB_DEBUG_ON?
no, these options have not been / are not enabled.
Can you please try it with those
On Fri, 14 May 2010 13:46:06 +0200 Steffen Klassert wrote:
Signed-off-by: Steffen Klassert steffen.klass...@secunet.com
---
include/linux/padata.h | 53
kernel/padata.c| 50 +++-
2 files