diff options
author | Alexander Polakov <apolyakov@beget.ru> | 2016-10-27 17:46:27 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-10-27 18:43:42 -0700 |
commit | 1bc11d70b5db7c6bb1414b283d7f09b1fe1ac0d0 (patch) | |
tree | 1b0345597ee77c8a116267bff15919cee540da20 /mm/nobootmem.c | |
parent | 21753583056d48a5fad964d6f272e28168426845 (diff) | |
download | linux-1bc11d70b5db7c6bb1414b283d7f09b1fe1ac0d0.tar.bz2 |
mm/list_lru.c: avoid error-path NULL pointer deref
As described in https://bugzilla.kernel.org/show_bug.cgi?id=177821:
After some analysis it seems to be that the problem is in alloc_super().
In case list_lru_init_memcg() fails it goes into destroy_super(), which
calls list_lru_destroy().
And in list_lru_init() we see that in case memcg_init_list_lru() fails,
lru->node is freed, but not set NULL, which then leads list_lru_destroy()
to believe it is initialized and call memcg_destroy_list_lru().
memcg_destroy_list_lru() in turn can access lru->node[i].memcg_lrus,
which is NULL.
[akpm@linux-foundation.org: add comment]
Signed-off-by: Alexander Polakov <apolyakov@beget.ru>
Acked-by: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/nobootmem.c')
0 files changed, 0 insertions, 0 deletions