lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <4F7408B7.9090706@jp.fujitsu.com> Date: Thu, 29 Mar 2012 16:01:11 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: Glauber Costa <glommer@...allels.com>, netdev@...r.kernel.org CC: David Miller <davem@...emloft.net>, Andrew Morton <akpm@...ux-foundation.org>, kamezawa.hiroyu@...fujitsu.com Subject: [BUGFIX][PATCH 0/3] memcg: tcp memcontrol fixes. I'm very sorry if you received this e-mail twice. == This series is 3 bugfixes for memcg's kmem.tcp memory controller. Maybe this should go via network tree. (CC akpm for noticing an ugly change in res_counter.) All patches are generated onto today linus's git tree. Brief description: Patch 1/3 .... tcp memcontrol doesn't see memcg's use_hierarchy value. Fix it. Patch 2/3 and 3/3 .... Because tcp memcontrol doesn't do any accounting when limit=RESOUCE_MAX, there will be account leakage when limit is changed. This can trigger WARN_ON() in res_counter which checks usage >= 0. Patch 2/3 .... don't call static_key_slow_dec(&memcg_socket_limit_enabled) until a cgroup under accounted is destroyed. Patch 3/3 .... add res_counter_uncharge_nowarn() to ignore leakage. Thanks, -Kame -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists