From nobody Fri Apr 01 20:51:37 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B16531A5F3F7 for ; Fri, 1 Apr 2022 20:51:42 +0000 (UTC) (envelope-from pho@FreeBSD.org) Received: from kaskal.pair.com (kaskal.pair.com [209.68.5.173]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4KVXQj4lKcz3rFk for ; Fri, 1 Apr 2022 20:51:41 +0000 (UTC) (envelope-from pho@FreeBSD.org) Received: from kaskal.pair.com (localhost [127.0.0.1]) by kaskal.pair.com (Postfix) with ESMTP id 0A8F5D656D3; Fri, 1 Apr 2022 16:51:41 -0400 (EDT) Received: from Peters-MacBook-Air.local (unknown [94.147.82.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by kaskal.pair.com (Postfix) with ESMTPSA id 7447FD8D6C8; Fri, 1 Apr 2022 16:51:40 -0400 (EDT) Date: Fri, 1 Apr 2022 22:51:37 +0200 From: Peter Holm To: Hans Petter Selasky Cc: freebsd-net Subject: Re: epoch callback panic Message-ID: References: <23673db5-5798-5c06-c04c-7c680ebe41d4@selasky.org> List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23673db5-5798-5c06-c04c-7c680ebe41d4@selasky.org> X-Rspamd-Queue-Id: 4KVXQj4lKcz3rFk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 209.68.5.173 is neither permitted nor denied by domain of pho@FreeBSD.org) smtp.mailfrom=pho@FreeBSD.org X-Spamd-Result: default: False [-2.83 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEFALL_USER(0.00)[pho]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-0.73)[-0.729]; NEURAL_HAM_LONG(-1.00)[-0.998]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[FreeBSD.org]; R_SPF_SOFTFAIL(0.00)[~all:c]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-net]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7859, ipnet:209.68.0.0/18, country:US]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, Apr 01, 2022 at 10:33:15PM +0200, Hans Petter Selasky wrote: > On 4/1/22 19:07, Peter Holm wrote: > > markj@ asked me to post this one: > > > > panic: rw lock 0xfffff801bccb1410 not unlocked > > cpuid = 4 > > time = 1648770125 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00e48a3d10 > > vpanic() at vpanic+0x17f/frame 0xfffffe00e48a3d60 > > panic() at panic+0x43/frame 0xfffffe00e48a3dc0 > > _rw_destroy() at _rw_destroy+0x35/frame 0xfffffe00e48a3dd0 > > in_lltable_destroy_lle_unlocked() at in_lltable_destroy_lle_unlocked+0x1a/frame 0xfffffe00e48a3df0 > > epoch_call_task() at epoch_call_task+0x13a/frame 0xfffffe00e48a3e40 > > gtaskqueue_run_locked() at gtaskqueue_run_locked+0xa7/frame 0xfffffe00e48a3ec0 > > gtaskqueue_thread_loop() at gtaskqueue_thread_loop+0xc2/frame 0xfffffe00e48a3ef0 > > fork_exit() at fork_exit+0x80/frame 0xfffffe00e48a3f30 > > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00e48a3f30 > > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > > > Details @ https://people.freebsd.org/~pho/stress/log/log0275.txt > > > > Hi, > > Maybe you need to grab the lock before destroying it? > This was on a pristine main-n254137-31190aa02eef0. > Is this easily reproducible? > No. I have only seen this once when running rsync between a nfs mount and a SU file system. - Peter > --HPS