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: <1264816777.2793.510.camel@tonnant> Date: Fri, 29 Jan 2010 20:59:37 -0500 From: Jon Masters <jonathan@...masters.org> To: linux-kernel <linux-kernel@...r.kernel.org> Cc: netdev <netdev@...r.kernel.org>, netfilter-devel <netfilter-devel@...r.kernel.org>, Eric Dumazet <eric.dumazet@...il.com>, Patrick McHardy <kaber@...sh.net> Subject: Re: debug: nt_conntrack and KVM crash On Fri, 2010-01-29 at 20:57 -0500, Jon Masters wrote: > Ah so I should have realized before but I wasn't looking at valid values > for the range of the hashtable yet, nf_conntrack_htable_size is getting > wildly out of whack. It goes from: > > (gdb) print nf_conntrack_hash_rnd > $1 = 2688505299 > (gdb) print nf_conntrack_htable_size > $2 = 16384 > > nf_conntrack_events: 1 > nf_conntrack_max: 65536 > > Shortly after booting, before being NULLed shortly after starting some > virtual machines (the hash isn't reset, whereas it is recomputed if the > hashtable is re-initialized after an intentional resizing operation): I mean the *seed* isn't changed, so I don't think it was resized intentionally. I wonder where else htable_size is fiddled with. Jon. -- 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