linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Glauber Costa <glommer@parallels.com>
Cc: linux-kernel@vger.kernel.org, paul@paulmenage.org,
	lizf@cn.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com,
	ebiederm@xmission.com, davem@davemloft.net, gthelen@google.com,
	netdev@vger.kernel.org, linux-mm@kvack.org, kirill@shutemov.name,
	avagin@parallels.com, devel@openvz.org
Subject: Re: [PATCH v5 6/8] tcp buffer limitation: per-cgroup limit
Date: Tue, 04 Oct 2011 14:48:55 +0200	[thread overview]
Message-ID: <1317732535.2440.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <1317730680-24352-7-git-send-email-glommer@parallels.com>

Le mardi 04 octobre 2011 A  16:17 +0400, Glauber Costa a A(C)crit :
> This patch uses the "tcp_max_mem" field of the kmem_cgroup to
> effectively control the amount of kernel memory pinned by a cgroup.
> 
> We have to make sure that none of the memory pressure thresholds
> specified in the namespace are bigger than the current cgroup.
> 
> Signed-off-by: Glauber Costa <glommer@parallels.com>
> CC: David S. Miller <davem@davemloft.net>
> CC: Hiroyouki Kamezawa <kamezawa.hiroyu@jp.fujitsu.com>
> CC: Eric W. Biederman <ebiederm@xmission.com>
> ---


> --- a/include/net/tcp.h
> +++ b/include/net/tcp.h
> @@ -256,6 +256,7 @@ extern int sysctl_tcp_thin_dupack;
>  struct mem_cgroup;
>  struct tcp_memcontrol {
>  	/* per-cgroup tcp memory pressure knobs */
> +	int tcp_max_memory;
>  	atomic_long_t tcp_memory_allocated;
>  	struct percpu_counter tcp_sockets_allocated;
>  	/* those two are read-mostly, leave them at the end */
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c

So tcp_max_memory is an "int".


> +static u64 tcp_read_limit(struct cgroup *cgrp, struct cftype *cft)
> +{
> +	struct mem_cgroup *memcg = mem_cgroup_from_cont(cgrp);
> +	return memcg->tcp.tcp_max_memory << PAGE_SHIFT;
> +}

1) Typical integer overflow here.

You need :

return ((u64)memcg->tcp.tcp_max_memory) << PAGE_SHIFT;


2) Could you add const qualifiers when possible to your pointers ?



--
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>

  reply	other threads:[~2011-10-04 12:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 12:17 [PATCH v5 0/8] per-cgroup tcp buffer pressure settings Glauber Costa
2011-10-04 12:17 ` [PATCH v5 1/8] Basic kernel memory functionality for the Memory Controller Glauber Costa
2011-10-04 12:17 ` [PATCH v5 2/8] socket: initial cgroup code Glauber Costa
2011-10-04 12:17 ` [PATCH v5 3/8] foundations of per-cgroup memory pressure controlling Glauber Costa
2011-10-04 12:17 ` [PATCH v5 4/8] per-cgroup tcp buffers control Glauber Costa
2011-10-04 12:17 ` [PATCH v5 5/8] per-netns ipv4 sysctl_tcp_mem Glauber Costa
2011-10-04 12:17 ` [PATCH v5 6/8] tcp buffer limitation: per-cgroup limit Glauber Costa
2011-10-04 12:48   ` Eric Dumazet [this message]
2011-10-05  8:08     ` Glauber Costa
2011-10-05  8:58       ` Eric Dumazet
2011-10-06  8:38         ` Glauber Costa
2011-10-04 12:17 ` [PATCH v5 7/8] Display current tcp memory allocation in kmem cgroup Glauber Costa
2011-10-04 12:18 ` [PATCH v5 8/8] Disable task moving when using kernel memory accounting Glauber Costa
2011-10-05  0:29 ` [PATCH v5 0/8] per-cgroup tcp buffer pressure settings KAMEZAWA Hiroyuki
2011-10-05  7:25   ` Glauber Costa
2011-10-07  8:05     ` KAMEZAWA Hiroyuki
2011-10-07  8:20       ` Glauber Costa
2011-10-07  8:55         ` KAMEZAWA Hiroyuki

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=1317732535.2440.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
    --to=eric.dumazet@gmail.com \
    --cc=avagin@parallels.com \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=glommer@parallels.com \
    --cc=gthelen@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul@paulmenage.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