netdev - [PATCH 0/2] Proposed fixes for tcp memory pressure

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1323941672-14324-1-git-send-email-glommer@parallels.com>
Date:	Thu, 15 Dec 2011 13:34:30 +0400
From:	Glauber Costa <glommer@...allels.com>
To:	davem@...emloft.net
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	cgroups@...r.kernel.org
Subject: [PATCH 0/2] Proposed fixes for tcp memory pressure

Hi,

I propose the following two fixes for the issues we're having in
linux-next.

The first one just moves the definition out of the CONFIG_INET,
and should fix the compile problems with allnoconfig.

The second one is a bit bigger, and takes away the socket
registration functions. As I've explained in the Changelog,
I believe this to be the saner way to do it. We need to do allocations
in both create and init time. 

This was compile tested with 4 different randconfigs, CGROUPS off,
KMEM cgroup off, INET off, all them on, and boot tested with
everything on.

Thanks.

Glauber Costa (2):
  Move limit definitions outside CONFIG_INET
  Explicitly call tcp creation and init from memcontrol.c

 include/linux/memcontrol.h   |    2 +-
 include/net/sock.h           |    2 --
 include/net/tcp_memcontrol.h |   19 ++++++++++++++++++-
 mm/memcontrol.c              |   13 ++++---------
 net/core/sock.c              |   37 -------------------------------------
 net/ipv4/tcp_memcontrol.c    |   11 ++++++-----
 6 files changed, 29 insertions(+), 55 deletions(-)

-- 
1.7.6.4

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