From owner-freebsd-bugs@freebsd.org Fri May 13 20:52:47 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D38DB39787 for ; Fri, 13 May 2016 20:52:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86FB41215 for ; Fri, 13 May 2016 20:52:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4DKqki9019744 for ; Fri, 13 May 2016 20:52:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209475] pf didn't check if enough free RAM for net.pf.states_hashsize Date: Fri, 13 May 2016 20:52:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: olivier@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 20:52:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209475 --- Comment #2 from Olivier Cochard --- If I configure net.pf.states_hashsize to 134,217,728, this mean using 10GB = of RAM on my 8GB only server, it will directly panic: KDB: stack backtrace: #0 0xffffffff807ecbb0 at kdb_backtrace+0x60 #1 0xffffffff807b4086 at vpanic+0x126 #2 0xffffffff807b3f53 at panic+0x43 #3 0xffffffff809b9b7b at vm_fault_hold+0x1bbb #4 0xffffffff80b3d10c at trap_pfault+0x19c #5 0xffffffff80b3c8fa at trap+0x47a #6 0xffffffff80b22de2 at calltrap+0x8 #7 0xffffffff81811509 at pf_initialize+0x1c9 #8 0xffffffff81826775 at pf_modevent+0x125 #9 0xffffffff8079e0db at module_register_init+0xfb #10 0xffffffff80793887 at linker_load_module+0xc07 #11 0xffffffff80794cd3 at kern_kldload+0xc3 #12 0xffffffff80794dab at sys_kldload+0x5b #13 0xffffffff80b3d817 at amd64_syscall+0x2f7 #14 0xffffffff80b230cb at Xfast_syscall+0xfb Uptime: 19s --=20 You are receiving this mail because: You are the assignee for the bug.=