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
| ||
|
Date: Wed, 03 Mar 2010 16:59:51 +0800 From: Zhu Yi <yi.zhu@...el.com> To: Eric Dumazet <eric.dumazet@...il.com> Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>, Arnaldo Carvalho de Melo <acme@...stprotocols.net>, "Pekka Savola (ipv6)" <pekkas@...core.fi>, Patrick McHardy <kaber@...sh.net>, Vlad Yasevich <vladislav.yasevich@...com>, Sridhar Samudrala <sri@...ibm.com>, Per Liden <per.liden@...csson.com>, Jon Maloy <jon.maloy@...csson.com>, Allan Stephens <allan.stephens@...driver.com>, Andrew Hendry <andrew.hendry@...il.com> Subject: Re: [PATCH 1/8] net: add limit for socket backlog On Wed, 2010-03-03 at 16:47 +0800, Eric Dumazet wrote: > Le mercredi 03 mars 2010 à 16:14 +0800, Zhu Yi a écrit : > > > I want to provide a method for protocols to set its sock backlog limit. > > For example, the sctp_rmem is 373500 (sysctl_sctp_rmem[1]) which is > > larger than (sysctl_rmem_default << 1). But I'm not very sure about the > > actual required size. So I didn't make it in the sctp patch. What do you > > think? > > I think this is not about bug fixes, but followup patches. > > We should first address the bug asap, then do further refinements later. I'm trying not to break the already working protocols which assume the backlog is unlimited. In your example, apparently define MINBACKLOG to 2048 is too small. Then what should it be? I'm waiting for responses from individual protocol maintainers. If all of them feel (sysctl_rmem_default << 1) is OK, I can remove the .limit and use it instead. Thanks, -yi -- 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