NetBSD Problem Report #56653

From christos@blinky.astron.com  Sat Jan 22 16:59:17 2022
Return-Path: <christos@blinky.astron.com>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 39A641A923A
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 22 Jan 2022 16:59:17 +0000 (UTC)
Message-Id: <20220122154212.99E6DA5DC10@blinky.astron.com>
Date: Sat, 22 Jan 2022 15:42:12 +0000 (UTC)
From: christos@netbsd.org
Reply-To: christos@netbsd.org
To: gnats-bugs@NetBSD.org
Subject: crash in ipv6 reassembly
X-Send-Pr-Version: 3.95

>Number:         56653
>Category:       kern
>Synopsis:       kernel crash in ipv6 fragment reassembly
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 22 17:00:01 +0000 2022
>Closed-Date:    Sun Dec 31 16:42:23 +0000 2023
>Last-Modified:  Sun Dec 31 16:42:23 +0000 2023
>Originator:     christos@netbsd.org
>Release:        NetBSD 9.99.91
>Organization:
	Maximal Entropy Inc,
>Environment:
System: NetBSD blinky.astron.com 9.99.91 NetBSD 9.99.91 (GENERIC) #79: Tue Oct 12 09:25:58 EDT 2021 christos@quasar.astron.com:/usr/src/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
	Kernel crashes in fragment re-assembly.
>How-To-Repeat:
	Configure a LOCKDEBUG kernel as a router, route IPv6 traffic,
	observe crash.
	#0  0xffffffff80226155 in cpu_reboot ()
	#1  0xffffffff80d10b07 in kern_reboot ()
	#2  0xffffffff80d56082 in vpanic ()
	#3  0xffffffff80d56147 in panic ()
	#4  0xffffffff80d4a4c8 in lockdebug_abort1 ()
	#5  0xffffffff80cfb688 in _kernel_lock ()
	#6  0xffffffff80a53c44 in frag6_fasttimo ()
	#7  0xffffffff80d8705a in pffasttimo ()
	#8  0xffffffff80d2f40e in callout_softclock ()
	#9  0xffffffff80d1f5fb in softint_dispatch ()
	#10 0xffffffff80220e3f in Xsoftintr ()
>Fix:
	Please!

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Fri, 07 Jul 2023 01:47:32 +0000
State-Changed-Why:
Last October, I added logic to make whatever CPU is hogging the kernel
lock crash via an IPI, so this should manifest differently now (if at
all, if we haven't fixed whatever was leaking it).  Have you seen any
`hogging kernel lock' on the same system since then?


State-Changed-From-To: feedback->closed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Sun, 31 Dec 2023 16:42:23 +0000
State-Changed-Why:
Diagnostics have changed so the underlying problem, which is not
related to IPv6 fragment reassembly, will manifest differently now
(and probably be more obvious about who's hogging the kernel lock).


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2024 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.