From nobody Thu Oct 10 11:16:49 2024 X-Original-To: freebsd-current@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 4XPRzX4jxMz5YsLY for ; Thu, 10 Oct 2024 11:16:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 4XPRzX2QyRz43bZ for ; Thu, 10 Oct 2024 11:16:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 49ABGn5k045903; Thu, 10 Oct 2024 14:16:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 49ABGn5k045903 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 49ABGnHK045902; Thu, 10 Oct 2024 14:16:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 10 Oct 2024 14:16:49 +0300 From: Konstantin Belousov To: Paul Floyd Cc: freebsd-current@freebsd.org Subject: Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Message-ID: References: <7bdb3c71-8a36-444e-8b1d-9c4f789fe638@gmail.com> <62745a68-9ed7-4f6f-bd6f-0ba3e10629c3@gmail.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <62745a68-9ed7-4f6f-bd6f-0ba3e10629c3@gmail.com> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4XPRzX2QyRz43bZ X-Spamd-Bar: ---- On Wed, Oct 09, 2024 at 07:34:31PM +0000, Paul Floyd wrote: > > > On 09-10-24 08:50, Konstantin Belousov wrote: > > > Perhaps you can check for the presence of the symbol exit@FBSD_1.0 in the > > backtrace to determine the situation. > > We don't read .gnu.version and the version number hasn't changed as far as I > can see. > > I can check osreldate to get an idea of the version. > > However this looks like it is going to be a lot more difficult. I need to be > able to tell apart abnormal termination (where no locks are to be expected) > and normal termination (one lock expected). > > If it's not possible/too difficult to work out how mnay locks should be > allowed on exit another option will be to try to fiddle around with what > happens during a call to exit(). That would mean something like ignoring the > lock count when called from exit(). > > And the last resort will be to just turn this check off. If you can determine not just the number of taken locks, but also the specific locks that were taken, perhaps you can check that this is the libc exit lock?