From nobody Wed Oct 9 08:27:22 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 4XNmGb3xkmz5Z0nw for ; Wed, 09 Oct 2024 08:27:35 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XNmGZ3c18z46y8 for ; Wed, 9 Oct 2024 08:27:34 +0000 (UTC) (envelope-from paulf2718@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=la3TtbGl; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2607:f8b0:4864:20::92b as permitted sender) smtp.mailfrom=paulf2718@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ua1-x92b.google.com with SMTP id a1e0cc1a2514c-84fb56d2fb2so213322241.3 for ; Wed, 09 Oct 2024 01:27:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728462453; x=1729067253; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Qs7bDw77OAWjTh/XFskYYJVN5277Vtuza0grryA3N5s=; b=la3TtbGlhOgQybouLCOzTSFDN07LxugtRd9VQJbIyXFrchwdRZRkdel9LNyyXMoHaM fQavzmtKdSrj2PydFpSubgm4cZ8w1WF74TXRlMofkUjkDB1G20ZomGMAwQ3UQPN0Uwbd G32E7BvPXpIII94m2jqXzlEuUQqLheUao2LqNXBBIrsz6ZgiFQOIuZhkY7JpG1ZRYy39 w+0Uyi4BGPKtg6wTLxTOeYOJrQmWsazRIKAnsnTbk070u7gSP5kPVCfU9Es/b/699zyw mcATv8jp8Hz51wX7aYJvXUgqdW04QUOyMLOrzWzC5uM69pYBk70Z3wHRRzhNveuQ1DOT 5yKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728462453; x=1729067253; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Qs7bDw77OAWjTh/XFskYYJVN5277Vtuza0grryA3N5s=; b=QOYYHCcHNgq7ikp5eirOgc/+V5kvNz/ALcxso9B9DSFVdfLYFG0dLbk31YJJRTdz8C uLSHm5pLN6S3bBoVEykoQ09ffuQ4BuZi5j9GRSR3OWOCb6W19T2RGCT4Sj1KPPWdgcfN +Vi93VYGmL7L4yW4VVw8wMWPMR3nYVsyengk7j+LROrKMtBFe1gK7/viP1F8FTB0Zk0G BQUoKrofRbS71sOgkX5knSYRVLwihLGZV9u7iFag3fVh9eeW3KwB7CivVuXUDwLt+095 6yHj7ceWT7+MdkkDXddW0wgWP9iffy/R1nKMDACwB0GcurG+xijxecMBamJtjAtGcqpi OXrA== X-Gm-Message-State: AOJu0YyyIJURuZLCAavh65QUbvhKB8eOXIcqhPtfBNtcFbgC1ch+Z5tj uBRzW7txSGBgtz8/DawklzRJs6UFpawuenpRTw1Orj+MvrAJsIQCTxxWFCB60sSrTezBiOPMJ0P GJYBmD6ZGyIPy2HU1PHU/BvzqqoJCQLoN X-Google-Smtp-Source: AGHT+IE6zKNY3tfpP3r5kq1Ih+l2/wRBTByv30CDQ9VOnREmvZNteqSrYxQ9PZHpCM+UvruBgtnr+FhCcX4vFLX+S5g= X-Received: by 2002:a05:6122:91d:b0:50c:4efb:835a with SMTP id 71dfb90a1353d-50cf09ab650mr730443e0c.1.1728462453437; Wed, 09 Oct 2024 01:27:33 -0700 (PDT) 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 References: <7bdb3c71-8a36-444e-8b1d-9c4f789fe638@gmail.com> In-Reply-To: From: Paul Floyd Date: Wed, 9 Oct 2024 10:27:22 +0200 Message-ID: Subject: Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008b7f2c062407069d" X-Spamd-Result: default: False [-3.77 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; NEURAL_HAM_SHORT(-0.78)[-0.776]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::92b:from] X-Rspamd-Queue-Id: 4XNmGZ3c18z46y8 X-Spamd-Bar: --- --0000000000008b7f2c062407069d Content-Type: text/plain; charset="UTF-8" > > On Wed, 9 Oct 2024 at 09:08, Konstantin Belousov > wrote: > On Wed, Oct 09, 2024 at 06:35:08AM +0000, Paul Floyd wrote: > > The biggest problem is with Helgrind. All apps now generate an extra > error > > > > ==68593== Thread #1: Exiting thread still holds 1 lock > > ==68593== at 0x4BBB5DA: _exit (in /lib/libsys.so.7) > > ==68593== by 0x49FC1C0: exit (in /lib/libc.so.7) > > ==68593== by 0x491CA10: __libc_start1 (in /lib/libc.so.7) > > ==68593== by 0x20182F: (below main) (crt1_s.S:83) > > This is intended, see 3f3ec4b99f79d32a0bf15495559ca9883bd751f2. > > Reply to list is better, Ug. I need to test but I don't think that I can simply add a default suppression for this as that would also mask any leaked user locks. I can probably check whether it's the main thread (I assume that this code doesn't run on subsidiary threads) and then only warn if there are 2 or more locks held. The next problem is that I don't see any way to tell whether I need to allow one lock or not. This is all userland so so __FreeBSD_version change. Also I don't see any public symbols. That just leaves me with configure time 'uname' checks. A+ Paul --0000000000008b7f2c062407069d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, 9 Oct 2024 at= 09:08, Konstantin Belousov <kostikbel@gmail.com> wrote:
On Wed, Oct 09, 2024 at 06:35:08AM +0000, Paul Floyd wr= ote:
> The biggest problem is with Helgrind. All apps now generate an= extra error
>
> =3D=3D68593=3D=3D Thread #1: Exiting thread st= ill holds 1 lock
> =3D=3D68593=3D=3D=C2=A0 =C2=A0 at 0x4BBB5DA: _exit= (in /lib/libsys.so.7)
> =3D=3D68593=3D=3D=C2=A0 =C2=A0 by 0x49FC1C0:= exit (in /lib/libc.so.7)
> =3D=3D68593=3D=3D=C2=A0 =C2=A0 by 0x491CA= 10: __libc_start1 (in /lib/libc.so.7)
> =3D=3D68593=3D=3D=C2=A0 =C2= =A0 by 0x20182F: (below main) (crt1_s.S:83)
=C2=A0
This is intended, see 3= f3ec4b99f79d32a0bf15495559ca9883bd751f2.


Reply to list is better,

Ug. I need t= o test but I don't think that I can simply add a default suppression fo= r this as that would also mask any leaked user locks.

<= div>I can probably check whether it's the main thread (I assume that th= is code doesn't run on subsidiary threads) and then only warn if there = are 2 or more locks held. The next problem is that I don't see any way = to tell whether I need to allow one lock or not. This is all userland so so= __FreeBSD_version change. Also I don't see any public symbols. That ju= st leaves me with configure time 'uname' checks.

A+
Paul=C2=A0
--0000000000008b7f2c062407069d--