Skip to contentSkip to conversation

minisocks: Use kmemdup and LIMIT_NETDEBUG

PATCH In review Arnaldo Carvalho de Melo 1 participant 1 message Nov 17, 2006

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 5/10 minisocks: Use kmemdup and LIMIT_NETDEBUG

Code diff stats:

[acme@newtoy net-2.6.20]$ codiff /tmp/tcp_minisocks.o.before /tmp/tcp_minisocks.o.after /pub/scm/linux/kernel/git/acme/net-2.6.20/net/ipv4/tcp_minisocks.c:
tcp_check_req | -44
1 function changed, 44 bytes removed
[acme@newtoy net-2.6.20]$

---
 net/ipv4/tcp_minisocks.c |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)
net/ipv4/tcp_minisocks.c +3 -4
index 383cb38..6dddf59 100644
@@ -351,8 +351,7 @@ #endif
 		 * socket up.  We've got bigger problems than
 		 * non-graceful socket closings.
 		 */
-		if (net_ratelimit())
-			printk(KERN_INFO "TCP: time wait bucket table overflow\n");
+		LIMIT_NETDEBUG(KERN_INFO "TCP: time wait bucket table overflow\n");
 	}
 
 	tcp_update_metrics(sk);
@@ -667,11 +666,11 @@ #ifdef CONFIG_TCP_MD5SIG
 				 * newsk structure. If we fail to get memory then we
 				 * end up not copying the key across. Shucks.
 				 */
-				char *newkey = kmalloc(key->keylen, GFP_ATOMIC);
+				char *newkey = kmemdup(key->key, key->keylen,
+						       GFP_ATOMIC);
 				if (newkey) {
 					if (!tcp_alloc_md5sig_pool())
 						BUG();
-					memcpy(newkey, key->key, key->keylen);
 					tp->af_specific->md5_add(child, child,
 								 newkey,
 								 key->keylen);
Signature · 1 line
1.4.2.1.g3d5c