diff options
| author | Eric Dumazet <eric.dumazet@gmail.com> | 2011-12-13 04:57:06 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-02-20 12:48:14 -0800 |
| commit | 16c7560fcca939095d099da4316f2df66aebc3ba (patch) | |
| tree | 62c6ca33a6d17069cc9028ecce53e18a87526618 /crypto | |
| parent | d3a6a79cfe7641d797ab74eea55b93e0f35f66d7 (diff) | |
| download | kernel_samsung_smdk4412-16c7560fcca939095d099da4316f2df66aebc3ba.zip kernel_samsung_smdk4412-16c7560fcca939095d099da4316f2df66aebc3ba.tar.gz kernel_samsung_smdk4412-16c7560fcca939095d099da4316f2df66aebc3ba.tar.bz2 | |
slub: fix a possible memleak in __slab_alloc()
commit 73736e0387ba0e6d2b703407b4d26168d31516a7 upstream.
Zhihua Che reported a possible memleak in slub allocator on
CONFIG_PREEMPT=y builds.
It is possible current thread migrates right before disabling irqs in
__slab_alloc(). We must check again c->freelist, and perform a normal
allocation instead of scratching c->freelist.
Many thanks to Zhihua Che for spotting this bug, introduced in 2.6.39
V2: Its also possible an IRQ freed one (or several) object(s) and
populated c->freelist, so its not a CONFIG_PREEMPT only problem.
Reported-by: Zhihua Che <zhihua.che@gmail.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Acked-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 'crypto')
0 files changed, 0 insertions, 0 deletions