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: <1291755776.21627.13.camel@bwh-desktop> Date: Tue, 07 Dec 2010 21:02:56 +0000 From: Ben Hutchings <bhutchings@...arflare.com> To: Eric Dumazet <eric.dumazet@...il.com> Cc: Martin Steigerwald <Martin@...htvoll.de>, linux-kernel@...r.kernel.org, netdev <netdev@...r.kernel.org> Subject: Re: bugs/regressions: report in LKML or in bugzilla? On Tue, 2010-12-07 at 17:12 +0100, Eric Dumazet wrote: > Le mardi 07 décembre 2010 à 16:39 +0100, Martin Steigerwald a écrit : > > > A participant of a linux performance training I hold found a bug with > > window scaling which did not receive any reply as well: > > > > Bug 20312 - System freeze with multiples of 32 in > > /proc/sys/net/ipv4/tcp_adv_win_scale > > https://bugzilla.kernel.org/show_bug.cgi?id=20312 > > > > User bug ? > > Documentation/networking/ip-sysctl.txt > > tcp_adv_win_scale - INTEGER > Count buffering overhead as bytes/2^tcp_adv_win_scale > (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale), > if it is <= 0. > Default: 2 > > Given we use 32bit numbers, using values outside of [-31 ... 31] makes litle sense. > > We could add sysctl range limit, but user should not mess with > /proc/sys/net/ipv4/parameters unless he knows what he is doing ? [...] For mere humans, the range is not quite os obvious. Which is why this has been fixed in net-2.6 (as noted on that bug report now). Ben. -- Ben Hutchings, Senior Software Engineer, Solarflare Communications Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- 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