From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Polakov <apolyakov@beget.ru>
Cc: bugzilla-daemon@bugzilla.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Vladimir Davydov <vdavydov@parallels.com>,
linux-mm@kvack.org, Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [Bug 177821] New: NULL pointer dereference in list_rcu
Date: Mon, 17 Oct 2016 17:10:38 -0700 [thread overview]
Message-ID: <20161017171038.924cbbcfc0a23652d2d2b8b4@linux-foundation.org> (raw)
In-Reply-To: <bug-177821-27@https.bugzilla.kernel.org/>
(resend due to "vdavydov@virtuozzo.com Unrouteable address")
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 17 Oct 2016 13:08:17 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=177821
>
> Bug ID: 177821
> Summary: NULL pointer dereference in list_rcu
Fair enough, I suppose.
Please don't submit patches via bugzilla - it is quite
painful. Documentation/SubmittingPatches explains the
way to do it.
Here's what I put together. Note that we do not have your
signed-off-by: for this. Please send it?
From: Alexander Polakov <apolyakov@beget.ru>
Subject: 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]
Cc: Vladimir Davydov <vdavydov@parallels.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/list_lru.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN mm/list_lru.c~a mm/list_lru.c
--- a/mm/list_lru.c~a
+++ a/mm/list_lru.c
@@ -554,6 +554,8 @@ int __list_lru_init(struct list_lru *lru
err = memcg_init_list_lru(lru, memcg_aware);
if (err) {
kfree(lru->node);
+ /* Do this so a list_lru_destroy() doesn't crash: */
+ lru->node = NULL;
goto out;
}
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-10-18 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-177821-27@https.bugzilla.kernel.org/>
2016-10-17 23:56 ` Andrew Morton
2016-10-18 0:10 ` Andrew Morton [this message]
2016-10-18 7:26 ` Alexander Polakov
2016-10-18 16:41 ` Vladimir Davydov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161017171038.924cbbcfc0a23652d2d2b8b4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apolyakov@beget.ru \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.com \
--cc=vdavydov@parallels.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox