From owner-freebsd-net@freebsd.org Fri Mar 26 23:46:30 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 333325B0BCB for ; Fri, 26 Mar 2021 23:46:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4F6dsf0pGkz3vbN for ; Fri, 26 Mar 2021 23:46:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 1B8525B0E17; Fri, 26 Mar 2021 23:46:30 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1B4AD5B097E for ; Fri, 26 Mar 2021 23:46:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F6dsf09nWz3vXW for ; Fri, 26 Mar 2021 23:46:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id ED8F2230B1 for ; Fri, 26 Mar 2021 23:46:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 12QNkTK6094905 for ; Fri, 26 Mar 2021 23:46:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 12QNkTPi094904 for net@FreeBSD.org; Fri, 26 Mar 2021 23:46:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 254303] Fatal trap 12: page fault while in kernel mode ((frr 7.5_1 + Freebsd 13 Beta3) zebra crashes server when routes are populated) Date: Fri, 26 Mar 2021 23:46:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: melifaro@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: melifaro@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-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2021 23:46:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254303 --- Comment #16 from Alexander V. Chernikov --- (In reply to Aleks from comment #15) Thank you! Short summary: >From the private core.5 you sent me: * rtentry looks perfectly fine, but the nexthop pointer is (mostly) zeroed * from the core2: failure to resolve nh_priv pointer * from the original kgdb_backtrace: nhg has zero pointer to nh_ctl So far it looks like we're removing the additional reference from the nexth= op group in some corner case scenario, which results in the group being freed, with the rtentry still pointing to this group. Re reproduction: I don't have 2 full-view peers, so I ended up duplicating = the feed from a single peer & introducing some delay, to mimic propagation dela= ys. So far I wasn't able to reproduce any panic. Are there any additional specifics (e.g. links flapping) in the setup? IS there any chance you could run stdbuf -o0 route -n monitor > zebra_log.txt at startup (or, actually, at the point in time when all peers are down) and then try to turn up first and th= en the second peer? If you could also run something like `while true; do date >> nhg.log ; netstat -4OnW >> nhg.log ; sleep 5; done` and share both files along with the core backtrace, that would be awesome. If there is a possibility of getting access to the server - that would real= ly speed the things up. --=20 You are receiving this mail because: You are on the CC list for the bug.=