From: Sha Zhengju <handai.szj@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sha Zhengju <handai.szj@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org
Subject: Re: [PATCH RESEND] memcg: Free spare array to avoid memory leak
Date: Thu, 03 May 2012 11:09:49 +0800 [thread overview]
Message-ID: <4FA1F6FD.7060100@gmail.com> (raw)
In-Reply-To: <20120501140314.1d7312fb.akpm@linux-foundation.org>
On 05/02/2012 05:03 AM, Andrew Morton wrote:
> On Thu, 19 Apr 2012 16:54:50 +0800
> Sha Zhengju<handai.szj@gmail.com> wrote:
>
>> From: Sha Zhengju<handai.szj@taobao.com>
>>
>> When the last event is unregistered, there is no need to keep the spare
>> array anymore. So free it to avoid memory leak.
> How serious is this leak? Is there any way in which it can be used to
> consume unbounded amounts of memory?
While registering events, the ->primary will apply for a larger array to
store
the new threshold info and the ->spare holds the old primary space.
But once unregistering event, the ->primary and ->spare pointer will be
swapped
after updating thresholds info. So if we have an eventfd with many(>1)
thresholds
attached to it, mem_cgroup_usage_unregister_event() will finally leave
->spare
holding a large array and have no chance to be freed.
I hope it is clear.
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -4412,6 +4412,12 @@ static void mem_cgroup_usage_unregister_event(struct cgroup *cgrp,
>> swap_buffers:
>> /* Swap primary and spare array */
>> thresholds->spare = thresholds->primary;
>> + /* If all events are unregistered, free the spare array */
>> + if (!new) {
>> + kfree(thresholds->spare);
>> + thresholds->spare = NULL;
>> + }
>> +
>> rcu_assign_pointer(thresholds->primary, new);
>>
> The resulting code is really quite convoluted. Try to read through it
> and follow the handling of ->primary and ->spare. Head spins.
>
> What is the protocol here? If ->primary is NULL then ->spare must also
> be NULL?
>
To be simple: if new(->primary) is NULL, it means we are unregistering
the last threshold and there is no need to keep ->spare any more.
So give the ->spare array a chance to be freed.
Thanks,
Sha
> I'll apply the patch, although I don't (yet) have sufficient info to
> know which kernels it should be applied to. Perhaps someone could
> revisit this code and see if it can be made more straightforward.
>
> .
>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-05-03 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 8:54 [PATCH RESEND] memcg: Free spare array to avoid memory leak Sha Zhengju
2012-05-01 21:03 ` Andrew Morton
2012-05-03 3:09 ` Sha Zhengju [this message]
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=4FA1F6FD.7060100@gmail.com \
--to=handai.szj@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).