From nobody Mon Jun 16 03:42:33 2025 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 4bLG6Q0gzsz5yQV7 for ; Mon, 16 Jun 2025 03:42:38 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta003.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bLG6P0jVSz45H2; Mon, 16 Jun 2025 03:42:37 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of cy.schubert@cschubert.com designates 3.97.99.32 as permitted sender) smtp.mailfrom=cy.schubert@cschubert.com; dmarc=permerror reason="p tag has invalid value: quarantine rua=mailto:p[ostmaster@cschubert.com" header.from=cschubert.com (policy=permerror) Received: from shw-obgw-4003a.ext.cloudfilter.net ([10.228.9.183]) by cmsmtp with ESMTPS id Ql6Fun1nU9JM2R0k0uEBko; Mon, 16 Jun 2025 03:42:36 +0000 Received: from spqr.komquats.com ([70.66.136.217]) by cmsmtp with ESMTPSA id R0jyu3DByWbOaR0jzuOFMx; Mon, 16 Jun 2025 03:42:36 +0000 X-Auth-User: cschuber X-Authority-Analysis: v=2.4 cv=Q5lx4J2a c=1 sm=1 tr=0 ts=684f92ac a=h7br+8Ma+Xn9xscxy5znUg==:117 a=h7br+8Ma+Xn9xscxy5znUg==:17 a=kj9zAlcOel0A:10 a=6IFa9wvqVegA:10 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=YxBL1-UpAAAA:8 a=mt9FY5lUz8t67Ick57cA:9 a=CjuIK1q_8ugA:10 a=LK5xJRSDVpKd5WXXoEvA:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id 2C078F72; Sun, 15 Jun 2025 20:42:34 -0700 (PDT) Received: by slippy.cwsent.com (Postfix, from userid 1000) id ED587134; Sun, 15 Jun 2025 20:42:33 -0700 (PDT) X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8+dev Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: freebsd-current@freebsd.org cc: emaste@freebsd.org, jrm@freebsd.org Subject: MIT KRB5 in 15-CURRENT 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 Date: Sun, 15 Jun 2025 20:42:33 -0700 Message-Id: <20250616034233.ED587134@slippy.cwsent.com> X-CMAE-Envelope: MS4xfKNQqOS77JnVaMmFuFiC6vwwimKgrvbYER1HKvCa5OKWr0ljsXt4omE9xSpKRo9i7XIVNQAaUJo32YzRHEN1pj7kLA8RR1cjcxMvt3bg3l9WzGBJctQM owhlEkFOFNSjRk8zrMz3FxlC+ZtNRzFMwaFtCh8AK14kRNG7f8L0EYmg5KF6rX5fcN03SRiZp3EOPXw8C9I9Jx2LGziHs5AIfnfFBAZNS1PAU0jFnaxBy1eU SDBOxX0Ea9NWeE78OZhy1wTL3Kl6cg/6WfMj8jW5XN8= X-Spamd-Result: default: False [1.17 / 15.00]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_SPAM_MEDIUM(0.97)[0.967]; NEURAL_HAM_SHORT(-0.90)[-0.900]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:3.97.99.32/31]; RCVD_IN_DNSWL_LOW(-0.10)[3.97.99.32:from]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_EQ_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US]; DMARC_BAD_POLICY(0.00)[cschubert.com : p tag has invalid value: quarantine rua=mailto:p[ostmaster@cschubert.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_THREE(0.00)[3] X-Rspamd-Queue-Id: 4bLG6P0jVSz45H2 X-Spamd-Bar: + Hi freebsd-current@, MIT KRB5 has been imported. It is disabled by default. To build and install MIT KRB5 in 15-CURRENT, 1. Add WITH_MITKRB5=yes in src.conf. 2. Do a buildworld and buildkernel. 3. Then installworld, run etcupdate to update files in /etc. 4. make delete-old and delete-old-libs. This is important. Skip this step and your resulting install will contain both MIT and Heimdal Kerberos. This will not work. Avoid using MIT KRB5 (for now) if you are running a Heimdal 1.5.2 KDC on FreeBSD. There is a procedure to convert the Heimdal HDB to an MIT KRB5 KDB. I am still working on documenting the procedure. The process is not straightforward as our Heimdal 1.5.2 is very old and does not support the feature found later versions of Heimdal needed to migrate the HDB to KDB. In a nutshell: one must export the HDB, import it into the latest version of Heimdal (using ports/security/heimdal), then export an MIT KRB5 export, and finally import it into a new MIT KRB5 KDB. If you use FreeBSD as part of an Active Directory domain, MIT KRB5 will simplify integration into a Microsoft network. You will still need to use winbind from samba or sssd, as Active Directory uses MIT KRB5 and LDAP for authentication. A ports exp-run will be needed to list any ports that may fail to build with MIT KRB5 in base. If any are found they will be fixed before we switch the default from Heimdal 1.5.2 to MIT KRB5 1.21.3. A decision to remove Heimdal from the source tree will come sometime after the default has been switched from Heimdal to MIT KRB5. I also expect some ports plumbing changes, especially in Mk/Uses/gssapi.mk in order to support MIT KRB5 in base. Any required changes should be identified with an exp-run. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e**(i*pi)+1=0 From nobody Mon Jun 16 04:28:49 2025 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 4bLH7v2XBTz5yT9B for ; Mon, 16 Jun 2025 04:28:59 +0000 (UTC) (envelope-from minsoochoo0122@proton.me) Received: from mail-4319.protonmail.ch (mail-4319.protonmail.ch [185.70.43.19]) (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 "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bLH7v09Nfz3dcK; Mon, 16 Jun 2025 04:28:58 +0000 (UTC) (envelope-from minsoochoo0122@proton.me) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1750048136; x=1750307336; bh=LE9Zlr4vtiKezcBFdvJFqGHGXgFhloOYGTaBBQWik2Y=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=kacyCYkULTDOA9udBUAXQYsMeD+jKrLvu/aY7vF8yD1b9SEuaOt74sTaRs45ywhGs dJkEfz4Yple006Q7cGsR6NhgyXMgQW+jE+6XE8PyS/qDECqqMVDVSYI3KSshUW+Aqp 0GYE6Vo3FYrQeRf3TPz1+YnvYzLJxZkj/dmEbmxsy4/c/Rk3UTmd9oePsqh6jrf2zg VApw82Os0gnKHo3d8TU9+k+gpm1t+itkkUf6yPub/AsPtKEb1eAMvwYB2kqYIEoANP YrnvjyW9qju9HtmgPNZFdmhDOI9er2rE2Ve7m+v6Ydn68AYqDU8+yF9haFGnhI3m2q VQR5HrbFYDUgg== Date: Mon, 16 Jun 2025 04:28:49 +0000 To: Cy Schubert From: Minsoo Choo Cc: freebsd-current@freebsd.org, emaste@freebsd.org, jrm@freebsd.org Subject: Re: MIT KRB5 in 15-CURRENT Message-ID: In-Reply-To: <20250616034233.ED587134@slippy.cwsent.com> References: <20250616034233.ED587134@slippy.cwsent.com> Feedback-ID: 45891198:user:proton X-Pm-Message-ID: 772d4311fbeb368c435db1b8ae24713d8e69aaea 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4bLH7v09Nfz3dcK X-Spamd-Bar: ---- 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:62371, ipnet:185.70.43.0/24, country:CH] On Sunday, June 15th, 2025 at 11:43 PM, Cy Schubert wrote: > Hi freebsd-current@, >=20 > MIT KRB5 has been imported. It is disabled by default. To build and insta= ll > MIT KRB5 in 15-CURRENT, >=20 > 1. Add WITH_MITKRB5=3Dyes in src.conf. >=20 > 2. Do a buildworld and buildkernel. >=20 > 3. Then installworld, run etcupdate to update files in /etc. >=20 > 4. make delete-old and delete-old-libs. This is important. Skip this step > and your > resulting install will contain both MIT and Heimdal Kerberos. This will > not work. >=20 > Avoid using MIT KRB5 (for now) if you are running a Heimdal 1.5.2 KDC on > FreeBSD. There is a > procedure to convert the Heimdal HDB to an MIT KRB5 KDB. I am still worki= ng > on documenting the procedure. The process is not straightforward as our > Heimdal 1.5.2 is very old and does not support the feature found later > versions of Heimdal needed to migrate the HDB to KDB. In a nutshell: one > must export the HDB, import it into the latest version of Heimdal (using > ports/security/heimdal), then export an MIT KRB5 export, and finally impo= rt > it into a new MIT KRB5 KDB. >=20 > If you use FreeBSD as part of an Active Directory domain, MIT KRB5 will > simplify integration into a Microsoft network. You will still need to use > winbind from samba or sssd, as Active Directory uses MIT KRB5 and LDAP fo= r > authentication. >=20 > A ports exp-run will be needed to list any ports that may fail to build > with MIT KRB5 in base. If any are found they will be fixed before we swit= ch > the default from Heimdal 1.5.2 to MIT KRB5 1.21.3. >=20 > A decision to remove Heimdal from the source tree will come sometime afte= r > the default has been switched from Heimdal to MIT KRB5. >=20 > I also expect some ports plumbing changes, especially in Mk/Uses/gssapi.m= k > in order to support MIT KRB5 in base. Any required changes should be > identified with an exp-run. >=20 >=20 > -- > Cheers, > Cy Schubert Cy.Schubert@cschubert.com >=20 > FreeBSD UNIX: cy@FreeBSD.org Web: https://FreeBSD.org >=20 > NTP: cy@nwtime.org Web: https://nwtime.org >=20 >=20 > e**(i*pi)+1=3D0 >=20 >=20 Thank you for your great work. I will close D43625 and D43624 as the adopti= on of MIT krb5 makes them obsolete. I have a few questions regarding to MIT krb5 replacing heimdal: 1. In which FreeBSD version will MIT krb5 be default? 2. In which FreeBSD version will heimdal be removed? Regards, Minsoo From nobody Mon Jun 16 05:01:56 2025 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 4bLHt01PMJz5yWWP for ; Mon, 16 Jun 2025 05:02:00 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta003.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bLHsz6Ssxz40Yh; Mon, 16 Jun 2025 05:01:59 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; none Received: from shw-obgw-4003a.ext.cloudfilter.net ([10.228.9.183]) by cmsmtp with ESMTPS id Ql6Fun1nU9JM2R1youEfXO; Mon, 16 Jun 2025 05:01:58 +0000 Received: from spqr.komquats.com ([70.66.136.217]) by cmsmtp with ESMTPSA id R1ynu3RcpWbOaR1youOIYZ; Mon, 16 Jun 2025 05:01:58 +0000 X-Auth-User: cschuber X-Authority-Analysis: v=2.4 cv=Q5lx4J2a c=1 sm=1 tr=0 ts=684fa546 a=h7br+8Ma+Xn9xscxy5znUg==:117 a=h7br+8Ma+Xn9xscxy5znUg==:17 a=kj9zAlcOel0A:10 a=6IFa9wvqVegA:10 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=YxBL1-UpAAAA:8 a=DAQKpz5FxlKkIvH-YIcA:9 a=CjuIK1q_8ugA:10 a=LK5xJRSDVpKd5WXXoEvA:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id B76CBFEB; Sun, 15 Jun 2025 22:01:56 -0700 (PDT) Received: by slippy.cwsent.com (Postfix, from userid 1000) id 82F661A3; Sun, 15 Jun 2025 22:01:56 -0700 (PDT) X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8+dev Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Minsoo Choo cc: Cy Schubert , freebsd-current@freebsd.org, emaste@freebsd.org, jrm@freebsd.org Subject: Re: MIT KRB5 in 15-CURRENT In-reply-to: References: <20250616034233.ED587134@slippy.cwsent.com> Comments: In-reply-to Minsoo Choo message dated "Mon, 16 Jun 2025 04:28:49 -0000." 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 Date: Sun, 15 Jun 2025 22:01:56 -0700 Message-Id: <20250616050156.82F661A3@slippy.cwsent.com> X-CMAE-Envelope: MS4xfNAK6XmzdaGxojyAt4sZ6RcsTBw7DRTZMF6VydrTw3H/iIPmpbgluoRZ8YmG81zRccpXDqSfSiJ9azIQ/w/Vo9AFIxEW2Pa25sN52PbxA13elMCtrRZo hpo4PMx3hiiHtZXpzGJ+xPotmh4uF0OnZr6XUEz9BOs/dd0cyVClzm+fNTUPrgL6liDvhhGIFK8G2gm7BWbFx8/W5woZoyJXxt1wM/NEdzuxdhkyhYqRz49M BPhiwXcXC8lXzRwBMxYhOdY1+trJa9TOrrFodHoyqmbLAOUEgsIuw9T3p9Q6VWYU9g9nT7qE//piC1U+DkhYAw== X-Rspamd-Queue-Id: 4bLHsz6Ssxz40Yh X-Spamd-Bar: ---- 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:16509, ipnet:3.96.0.0/15, country:US] In message , Minsoo Choo writes: > On Sunday, June 15th, 2025 at 11:43 PM, Cy Schubert com> wrote: > > > Hi freebsd-current@, > >=20 > > MIT KRB5 has been imported. It is disabled by default. To build and insta= > ll > > MIT KRB5 in 15-CURRENT, > >=20 > > 1. Add WITH_MITKRB5=3Dyes in src.conf. > >=20 > > 2. Do a buildworld and buildkernel. > >=20 > > 3. Then installworld, run etcupdate to update files in /etc. > >=20 > > 4. make delete-old and delete-old-libs. This is important. Skip this step > > and your > > resulting install will contain both MIT and Heimdal Kerberos. This will > > not work. > >=20 > > Avoid using MIT KRB5 (for now) if you are running a Heimdal 1.5.2 KDC on > > FreeBSD. There is a > > procedure to convert the Heimdal HDB to an MIT KRB5 KDB. I am still worki= > ng > > on documenting the procedure. The process is not straightforward as our > > Heimdal 1.5.2 is very old and does not support the feature found later > > versions of Heimdal needed to migrate the HDB to KDB. In a nutshell: one > > must export the HDB, import it into the latest version of Heimdal (using > > ports/security/heimdal), then export an MIT KRB5 export, and finally impo= > rt > > it into a new MIT KRB5 KDB. > >=20 > > If you use FreeBSD as part of an Active Directory domain, MIT KRB5 will > > simplify integration into a Microsoft network. You will still need to use > > winbind from samba or sssd, as Active Directory uses MIT KRB5 and LDAP fo= > r > > authentication. > >=20 > > A ports exp-run will be needed to list any ports that may fail to build > > with MIT KRB5 in base. If any are found they will be fixed before we swit= > ch > > the default from Heimdal 1.5.2 to MIT KRB5 1.21.3. > >=20 > > A decision to remove Heimdal from the source tree will come sometime afte= > r > > the default has been switched from Heimdal to MIT KRB5. > >=20 > > I also expect some ports plumbing changes, especially in Mk/Uses/gssapi.m= > k > > in order to support MIT KRB5 in base. Any required changes should be > > identified with an exp-run. > >=20 > >=20 > > -- > > Cheers, > > Cy Schubert Cy.Schubert@cschubert.com > >=20 > > FreeBSD UNIX: cy@FreeBSD.org Web: https://FreeBSD.org > >=20 > > NTP: cy@nwtime.org Web: https://nwtime.org > >=20 > >=20 > > e**(i*pi)+1=3D0 > >=20 > >=20 > > Thank you for your great work. I will close D43625 and D43624 as the adopti= > on of MIT krb5 makes them obsolete. > > I have a few questions regarding to MIT krb5 replacing heimdal: > 1. In which FreeBSD version will MIT krb5 be default? 15-RELEASE. > 2. In which FreeBSD version will heimdal be removed? Hopefully 15-RELEASE though 16-RELEASE could be likely. > > Regards, > Minsoo -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e**(i*pi)+1=0 From nobody Mon Jun 16 18:03:44 2025 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 4bLdDy50Gtz5yD2k for ; Mon, 16 Jun 2025 18:04:34 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [IPv6:2001:1640:5::8:31]) (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 4bLdDx1C8Zz3tw7 for ; Mon, 16 Jun 2025 18:04:33 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=gKMruH8D; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 2001:1640:5::8:31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 0ABC8240DEF for ; Mon, 16 Jun 2025 20:04:25 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 68D4C240491 for ; Mon, 16 Jun 2025 20:04:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1750097063; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=f/pMKtjropa6O8qNDucYvakz0rDRePcCi99xQcXVW/k=; b=gKMruH8DbfGoGjWAP5rjyVa3Q50CAryQoh5oTaePy7wRrx67FD7dGQUqezSCp4oMNeyB5B vDVCUkaI+f6a2JsS+yb3Hny3DesDeTS3BnkUEkO6OV7l6F1PmrTVPsJViGha6ZUGjXtMfi ajKuauGnfjG0GQxBgjHycO8QdcJGsOpWwZDbZs/5Z1vNd4fJFy5wCl26QmAyXZCtFmJ3yp 6tityTdLKkh1TxZn/gIrRB4M2f4DrRDgcL39T0MUVvQNsmGveeYno6E/THSiCBXShKCYGD Ac5JjTv4eIshOm7f7SzV+RoFkBSBoSwXKo1IvIBevDkBDE3/dXP2x4WbvmaeRg== Received: from thor.sb211.local (dynamic-2a02-3100-187a-8502-e9d8-02e7-65ee-7370.310.pool.telefonica.de [IPv6:2a02:3100:187a:8502:e9d8:2e7:65ee:7370]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 2F0F424048E for ; Mon, 16 Jun 2025 20:04:23 +0200 (CEST) Date: Mon, 16 Jun 2025 20:03:44 +0200 From: A FreeBSD User To: FreeBSD CURRENT Subject: kldload: an error occurred while loading module linux. Message-ID: <20250616200411.610e2b18@thor.sb211.local> 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: multipart/signed; boundary="Sig_/FxMAbq4xSdEbRuP.q1lZTBe"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 6c5683 X-Rspamd-UID: 4fa96c X-Spamd-Result: default: False [-4.96 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.93)[-0.932]; NEURAL_HAM_MEDIUM(-0.43)[-0.434]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+ip6:2001:1640:5::8:0/112]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DMARC_NA(0.00)[walstatt-de.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4bLdDx1C8Zz3tw7 X-Spamd-Bar: ---- --Sig_/FxMAbq4xSdEbRuP.q1lZTBe Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, after upgrading today to=20 FreeBSD 15.0-CURRENT #1 master-n278000-e4988ba172a8: Mon Jun 16 19:25:44 CE= ST 2025 amd64 loading module "linux.ko" fails: # kldload linux kldload: an error occurred while loading module linux. Please check dmesg(8= ) for more details. dmesg [...] link_elf_obj: symbol elf32_register_note undefined linker_load_file: /boot/kernel/linux.ko - unsupported file type The real funny part is, that linux64.ko and linux_common.ko are loaded as e= xpected: # kldstat Id Refs Address Size Name 1 23 0xffffffff80200000 1d35670 kernel 3 1 0xffffffff82820000 2e478 linux64.ko 4 3 0xffffffff8284f000 d038 linux_common.ko 5 1 0xffffffff8285d000 3390 acpi_wmi.ko 6 1 0xffffffff82861000 73c0 linprocfs.ko 7 1 0xffffffff82869000 440c linsysfs.ko WITH_KRB5=3Dyes in /etc/src.conf Kind regards and thanks in advance, oh --=20 A FreeBSD user --Sig_/FxMAbq4xSdEbRuP.q1lZTBe Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaFBcmwAKCRCxzvs8Oqok rzesAQCQmgsursyHW5utTwrz1++NUgM+xWtBsDioXQmFqpdP1gEA0AB1OBCPXEu0 RxL5C0wNbSxeINeGNJik29IFgi8/1Ak= =l4mp -----END PGP SIGNATURE----- --Sig_/FxMAbq4xSdEbRuP.q1lZTBe-- From nobody Tue Jun 17 07:47:28 2025 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 4bLzVk2T5Gz5q1wX for ; Tue, 17 Jun 2025 07:47:42 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [85.220.129.31]) (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 4bLzVh2cM0z3r1w for ; Tue, 17 Jun 2025 07:47:40 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=AfDEdxd1; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 4A45E240D46 for ; Tue, 17 Jun 2025 09:47:38 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 76514240269 for ; Tue, 17 Jun 2025 09:47:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1750146456; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FVYwW4tsIHJqylWhMqV9oFYV3AvJm86d+oqYHkMm/DE=; b=AfDEdxd1MVlv+xvgcoM30lbZezTxu0nTMTPgeOLs45K1ccpzh3J8QdezpWc9a0fmrC2S0n TNl+C7Jh74J0nabmWPBAO7NoXwshPAVxZZ2JljxvMaowGmPR3oGnmZ9r0PXh1uioyy0b3k KNO+5z0Z7wcslPn0oLOY2eMnc8hD3jpm8hOtTLSmfh4ZuT/JzhvpzsgBcHirwipCjQCDnw vx75Zf0/FJAoiVDu+uxy0QBONGpfg8lL0RhMD6qpDvZX67vo+Z/LyWlKTchZ11ks90F/W7 qtLM6IId4OmT6AbIP/FKaqe7LYiDj7RnL87eazZM/wtXbKwHooAVln+T3tG0NA== Received: from freyja (p4fc0a637.dip0.t-ipconnect.de [79.192.166.55]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 30D792404A2 for ; Tue, 17 Jun 2025 09:47:36 +0200 (CEST) Date: Tue, 17 Jun 2025 09:47:28 +0200 From: FreeBSD User To: FreeBSD CURRENT Subject: Re: kldload: an error occurred while loading module linux. Message-ID: <20250617094728.6a8d62f1@freyja> In-Reply-To: <20250616200411.610e2b18@thor.sb211.local> References: <20250616200411.610e2b18@thor.sb211.local> Organization: Heimstatt X-Mailer: Claws Mail 4.3.0 (GTK 3.24.49; amd64-portbld-freebsd14.3) 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-Transfer-Encoding: 7bit X-Rspamd-UID: a6311c X-Rspamd-UID: 7cd30a X-Spamd-Result: default: False [-2.17 / 15.00]; NEURAL_HAM_LONG(-0.98)[-0.980]; NEURAL_HAM_MEDIUM(-0.77)[-0.772]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_HAM_SHORT(-0.32)[-0.317]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.31:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[walstatt-de.de]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4bLzVh2cM0z3r1w X-Spamd-Bar: -- On Mon, 16 Jun 2025 20:03:44 +0200 A FreeBSD User wrote: Irecall this and call myself a bit confused ... By accident, I disabled the 32bit compatibility in the kernel config. oh > Hello, > > after upgrading today to > FreeBSD 15.0-CURRENT #1 master-n278000-e4988ba172a8: Mon Jun 16 > 19:25:44 CEST 2025 amd64 > > loading module "linux.ko" fails: > > # kldload linux > kldload: an error occurred while loading module linux. Please check > dmesg(8) for more details. > > > dmesg > [...] > link_elf_obj: symbol elf32_register_note undefined > linker_load_file: /boot/kernel/linux.ko - unsupported file type > > The real funny part is, that linux64.ko and linux_common.ko are > loaded as expected: # kldstat > Id Refs Address Size Name > 1 23 0xffffffff80200000 1d35670 kernel > 3 1 0xffffffff82820000 2e478 linux64.ko > 4 3 0xffffffff8284f000 d038 linux_common.ko > 5 1 0xffffffff8285d000 3390 acpi_wmi.ko > 6 1 0xffffffff82861000 73c0 linprocfs.ko > 7 1 0xffffffff82869000 440c linsysfs.ko > > > WITH_KRB5=yes in /etc/src.conf > > Kind regards and thanks in advance, > oh > > > From nobody Tue Jun 17 14:52:34 2025 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 4bM8wy3j4Gz5yQsr; Tue, 17 Jun 2025 14:52:34 +0000 (UTC) (envelope-from ivy@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bM8wy2nsZz3PXx; Tue, 17 Jun 2025 14:52:34 +0000 (UTC) (envelope-from ivy@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750171954; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=agn3ZJ7umf3tvbDGdcP+28zrl0oQgsN3ogFZNpnTIpg=; b=O9HT33E83Dlr+itWTlXGF03guWN1cugS7bRdbf0DWurTpGAqUZcs/cAjoBpc5DWYjTIIvU Rlea2EFeHtUDmaaokijsFki5szM0CLUChML4Fq4ocxqCAN4yUAes4v8Dioy8rGPjne9krG qJKHGU6j3ZtBkSYutt885Lyb0uzC7nWRmltTuQRbzeTkePx48SdxNvMbuXYXBq6IXetcSe rYbMdxPcieGTazj5qXcTtNwJAjkyv5bcaQ4me5cfWUIrmqjqIA3p/UhOaOxhR1XmruQmtM GBjec9b4KMdjd9YPBkLMn/t6OMaFxC7trE+/BtqyWPF4Sg6p41MlS9667PQAMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750171954; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=agn3ZJ7umf3tvbDGdcP+28zrl0oQgsN3ogFZNpnTIpg=; b=XbsKEi2uKWxBUCwBodI+65ck8vi8ZryiacBwHEMKLoSvU6d+Sl1qlt0j+Tja7wA13ek552 4NPAhHjYQVJglcIq14xB1ErHuQI5rM8pvKhSvGZf6k7ONbpvYJUCcf3XJMVwsQmsucIlXs xw/oo3gdBU2P2KCnKgpAfmZftWRK7rP4UU1+uC1OiPhtg0Ov8KgFwj9rSzeMfn5Km6PeH6 NqjcveOxBVMG9s+yyxnWQmDIIgV+H5zf+EoeFkaHiP4KFrUKaKEseeKn+EgXi5vYk9KZMz QcdT/1i9mOMIYyBWLd7jBIP7/W3C7GiofrqS+S1uNc4d46EoLKP2dSfaQShtTA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1750171954; a=rsa-sha256; cv=none; b=UbkReY6GMSe00brE6yY3iX9NCqSi5oYQwuwccO1TuS/OGMXrClQ7ZbzunzzR12mwKlDfVL bV3hXUginzerq9g+9hBjFfFe3QeweaINPIrnfdu1+FBWrtNoUQLFEJC7c8pnPzUT+f/K8P KcsPKuSmAEOeb24xe2nIqkm0ettbFIRmcg4Ukcc0ZQ61xufMw5vViTA35rm3CSsm9Y6KCM ZHhktacxb88wv/AZRNqFJoE+AMH/NVK2bM8k0iek070T7FoqOX/dFUZzKPFF3F7JRHAZx6 1rDzpffkojchBBqFfFHEYZY4V8YtlocLXHdYWHgpIMVdLZqDqMCy+KjCv4S9pg== Received: by freefall.freebsd.org (Postfix, from userid 1532) id 5531E14BAE; Tue, 17 Jun 2025 14:52:34 +0000 (UTC) Date: Tue, 17 Jun 2025 15:52:34 +0100 From: Lexi Winter To: FreeBSD User Cc: FreeBSD CURRENT , net@freebsd.org Subject: Re: if_bridge(): IPv6 EUI-64 seemingly not working Message-ID: Mail-Followup-To: FreeBSD User , FreeBSD CURRENT , net@freebsd.org References: <20250611072836.2a0b026a@thor.sb211.local> <20250612073301.60bfc7ce@freyja> 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UTexeVv8VMUjII3E" Content-Disposition: inline In-Reply-To: <20250612073301.60bfc7ce@freyja> --UTexeVv8VMUjII3E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable FreeBSD User: > net.link.bridge.inherit_mac: 1 > [...] >=20 > ether 4c:52:62:2b:05:eb > inet6 fe80::5a9c:fcff:fe00:393a%bridge0 prefixlen 64 scopeid 0x6 i was able to reproduce this: # sysctl net.link.bridge.inherit_mac=3D1 net.link.bridge.inherit_mac: 0 -> 1 # ifconfig bridge1 create inet6 -ifdisabled auto_linklocal up # ifconfig bridge1 | egrep 'ether|inet6' ether 58:9c:fc:10:43:03 inet6 fe80::5a9c:fcff:fe10:4303%bridge1 prefixlen 64 scopeid 0xa # ifconfig epair create epair2a # ifconfig bridge1 addm epair2a # ifconfig bridge1 | egrep 'ether|inet6' ether 02:36:0f:34:6b:0a inet6 fe80::5a9c:fcff:fe10:4303%bridge1 prefixlen 64 scopeid 0xa some observations: - i don't think this is caused directly by the member_ifaddrs changes. - you can work around the problem by manually setting the bridge link address when creating it instead of using inherit_mac, i.e.: ifconfig bridge1 create link 02:00:00:00:00:01 - i don't think this is a bug per se, it's more that we simply don't update the IPv6 lladdr when an interface's MAC address changes. but i've copied net@ in case anyone else has an opinion on this. --UTexeVv8VMUjII3E Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaFGBLgAKCRD1nT63mIK/ YLI8AP9hncM2JjVsP1PQd6aF/Vwp7llsEY13rvKeGa5mU4GEbgEAousgOHpwivk3 ObaAsb+xCgwoB8XOU1ELsocfRObGSgo= =eyiL -----END PGP SIGNATURE----- --UTexeVv8VMUjII3E-- From nobody Tue Jun 17 16:57:23 2025 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 4bMCjj757Mz5VbY7; Tue, 17 Jun 2025 16:58:01 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (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 4bMCjj4LySz4LnT; Tue, 17 Jun 2025 16:58:01 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 1E133240A05; Tue, 17 Jun 2025 18:57:59 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 852C2240165; Tue, 17 Jun 2025 18:57:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1750179477; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dOhiuC2xogvrMfuHxQO5c11jhl1SbxeTohw4FE1rhV8=; b=lemz/FeIGtHYfzKccB1AsL3HeO3KR5yKHIb5yZ2IYUR5rphtceMd8a1XiSPchEGoQo3CIZ 1Uq4HiPa1ggyM7aI6uNmZZyeQcpB39SWbMhcFErcMaZH24YyOcdIY+O64sC/XgULg3d5PL Bnk83Le1FiZNOwTB1p1C1zfjekoTD7OxOAVcYQc5keXU035KBWBudBA797hGxBlE5WTpnx ewtqimdothzlTn0iotGAF5tIvrpo68H2bC66FBSP2taeUOnk1+lnT6k1iJLpdsYGRXcpz1 yOcuX7uzMOhd5xYS3SNW0HeUvPeXIKM3+cCJp+W5IcyI00ncmCiCavC28PrZ2w== Received: from thor.sb211.local (dynamic-2a02-3100-2e61-4702-9121-a17e-f14b-6ada.310.pool.telefonica.de [IPv6:2a02:3100:2e61:4702:9121:a17e:f14b:6ada]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 2AD3F240116; Tue, 17 Jun 2025 18:57:57 +0200 (CEST) Date: Tue, 17 Jun 2025 18:57:23 +0200 From: A FreeBSD User To: Lexi Winter Cc: FreeBSD CURRENT , net@freebsd.org Subject: Re: if_bridge(): IPv6 EUI-64 seemingly not working Message-ID: <20250617185750.55eba7e8@thor.sb211.local> In-Reply-To: References: <20250611072836.2a0b026a@thor.sb211.local> <20250612073301.60bfc7ce@freyja> 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: multipart/signed; boundary="Sig_/BAg8d4_h4kawfiMgnDe7x81"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 8dd7b0 X-Rspamd-UID: 033f90 X-Rspamd-Queue-Id: 4bMCjj4LySz4LnT X-Spamd-Bar: ---- 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:25394, ipnet:85.220.128.0/17, country:DE] --Sig_/BAg8d4_h4kawfiMgnDe7x81 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Tage des Herren Tue, 17 Jun 2025 15:52:34 +0100 Lexi Winter schrieb: > FreeBSD User: > > net.link.bridge.inherit_mac: 1 > > [...] > >=20 > > ether 4c:52:62:2b:05:eb > > inet6 fe80::5a9c:fcff:fe00:393a%bridge0 prefixlen 64 scopeid 0x= 6 =20 >=20 > i was able to reproduce this: First of all, thank you very much for checking this. >=20 > # sysctl net.link.bridge.inherit_mac=3D1 > net.link.bridge.inherit_mac: 0 -> 1 > # ifconfig bridge1 create inet6 -ifdisabled auto_linklocal up > # ifconfig bridge1 | egrep 'ether|inet6' > ether 58:9c:fc:10:43:03 > inet6 fe80::5a9c:fcff:fe10:4303%bridge1 prefixlen 64 scopeid 0xa > # ifconfig epair create > epair2a > # ifconfig bridge1 addm epair2a > # ifconfig bridge1 | egrep 'ether|inet6' > ether 02:36:0f:34:6b:0a > inet6 fe80::5a9c:fcff:fe10:4303%bridge1 prefixlen 64 scopeid 0xa >=20 > some observations: >=20 > - i don't think this is caused directly by the member_ifaddrs changes. >=20 > - you can work around the problem by manually setting the bridge link > address when creating it instead of using inherit_mac, i.e.: > ifconfig bridge1 create link 02:00:00:00:00:01 >=20 > - i don't think this is a bug per se, it's more that we simply don't > update the IPv6 lladdr when an interface's MAC address changes. > but i've copied net@ in case anyone else has an opinion on this. I'd dare to disaggree, we have running several recent CURRENT and 14-STABLE= boxes (almost every 2nd day recompiled world/kernel) with very close configuration scheme= s (according to kernel config and NIC/bridge config as far it is possible to say so with re= spect to the different OS and different network addresses). On 14-STABLE with very simil= ar jail configuration I do NOT see this (mis)behaviour of if_bridge().=20 --=20 A FreeBSD user --Sig_/BAg8d4_h4kawfiMgnDe7x81 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaFGejgAKCRCxzvs8Oqok rxQKAP4wu3mzc457wP1gM3wreYHJukfO0vQmIYu6aOG+aoGi0AEA/DuqcI1JeOMf WF6OYthKizsfniNAwd/lLahbg/75EwY= =6Xx8 -----END PGP SIGNATURE----- --Sig_/BAg8d4_h4kawfiMgnDe7x81-- From nobody Wed Jun 18 08:03:01 2025 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 4bMbpB1lyhz5yPVc; Wed, 18 Jun 2025 08:03:14 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (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 4bMbp96pGgz3Wst; Wed, 18 Jun 2025 08:03:13 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 413E8240AA2; Wed, 18 Jun 2025 10:03:12 +0200 (CEST) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 63FF72405D8; Wed, 18 Jun 2025 10:03:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1750233790; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6dD7otCl9bUdKRuVxpIDsrD/KJakI2k6mYqlgXjEW/c=; b=Q1+dcqHuM7AFHLbuCSQcSUokdxENExj9j7rB8WsRF7XE1P6IJRoAk3ft3NsZi+sZOUQCZF WxE8x6u9bqJAIqauFbGrC9tEH7adoNbtQCVqpVneEhPLjoT/L2HpQuGPiBPiI+DxUIF711 /a3LMVDGODM2fFrxofXPHUoX3FdhlFmCy6BjWts1wjVHWdF7CE5zZwxFQRVb+q5/TlgGcw iWWyFOD/raLePm0NkEY1bl7RAs/BJfCfcy9f23g3DhY28s1HESo3bQngKyHJNCCedmGjNv f2o1ViOqAoIBkBSRZRY6ZkeKHsZ6nWHmTct77y9DowGs2mla+3lqreNR2ho7qA== Received: from freyja (p4fc0a637.dip0.t-ipconnect.de [79.192.166.55]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 0CAEE240562; Wed, 18 Jun 2025 10:03:10 +0200 (CEST) Date: Wed, 18 Jun 2025 10:03:01 +0200 From: FreeBSD User To: Lexi Winter Cc: FreeBSD CURRENT , net@freebsd.org Subject: Re: if_bridge(): IPv6 EUI-64 seemingly not working Message-ID: <20250618100301.57af0cd1@freyja> In-Reply-To: References: <20250611072836.2a0b026a@thor.sb211.local> <20250612073301.60bfc7ce@freyja> Organization: Heimstatt X-Mailer: Claws Mail 4.3.0 (GTK 3.24.49; amd64-portbld-freebsd14.3) 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-Transfer-Encoding: 7bit X-Rspamd-UID: f40a13 X-Rspamd-UID: 951b29 X-Rspamd-Queue-Id: 4bMbp96pGgz3Wst X-Spamd-Bar: ---- 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:25394, ipnet:85.220.128.0/17, country:DE] On Tue, 17 Jun 2025 15:52:34 +0100 Lexi Winter wrote: > FreeBSD User: > > net.link.bridge.inherit_mac: 1 > > [...] > > > > ether 4c:52:62:2b:05:eb > > inet6 fe80::5a9c:fcff:fe00:393a%bridge0 prefixlen 64 > > scopeid 0x6 > > i was able to reproduce this: > > # sysctl net.link.bridge.inherit_mac=1 > net.link.bridge.inherit_mac: 0 -> 1 > # ifconfig bridge1 create inet6 -ifdisabled auto_linklocal up > # ifconfig bridge1 | egrep 'ether|inet6' > ether 58:9c:fc:10:43:03 > inet6 fe80::5a9c:fcff:fe10:4303%bridge1 prefixlen 64 scopeid > 0xa # ifconfig epair create > epair2a > # ifconfig bridge1 addm epair2a > # ifconfig bridge1 | egrep 'ether|inet6' > ether 02:36:0f:34:6b:0a > inet6 fe80::5a9c:fcff:fe10:4303%bridge1 prefixlen 64 scopeid > 0xa > > some observations: > > - i don't think this is caused directly by the member_ifaddrs changes. > > - you can work around the problem by manually setting the bridge link > address when creating it instead of using inherit_mac, i.e.: > ifconfig bridge1 create link 02:00:00:00:00:01 Confirmed: this workaround, in rc.conf represented via create_args_brisgeX="ether XX:XX:XX:XX:XX:XX" sets linklocal adress according the inherited/forced MAC address and later on via rtsol set the EUI64 host portion correct as desired (on CURRENT, not workaround needed on recent 14-STABLE, as reported). > > - i don't think this is a bug per se, it's more that we simply don't > update the IPv6 lladdr when an interface's MAC address changes. > but i've copied net@ in case anyone else has an opinion on this. From nobody Thu Jun 19 14:46:08 2025 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 4bNNjd1JsSz5ym1J for ; Thu, 19 Jun 2025 14:47:01 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (3072 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bNNjb4RxNz3wD2 for ; Thu, 19 Jun 2025 14:46:59 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.de header.s=s31663417 header.b="iz/9Gf7s"; spf=pass (mx1.freebsd.org: domain of garyj@gmx.de designates 212.227.15.18 as permitted sender) smtp.mailfrom=garyj@gmx.de; dmarc=pass (policy=quarantine) header.from=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1750344417; x=1750949217; i=garyj@gmx.de; bh=DnK9SeMUJ99IRs5PLKHoLW+sb2aAAQHno60RGgwvNW0=; h=X-UI-Sender-Class:Date:From:To:Subject:Message-ID:Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=iz/9Gf7s+H68vSE4yRu7KS7NK+81j0SIrVzqEA2dpVSPOALfsV0GQziqeVkxLCqE Ivw/fCVFMmylJzJatE5gjUN6eLbRQF14yDRQExZjCpK4mTS6pL/hPQQCCBDFcKWxa Z6Cn42FfX70DNUDFutXVBbDBfL0uNDZrW4YgHZRqEFBbtVrAUbHWUb6f4UiGSTf2j EIsrpCf6qxjN5Uz+x3bc3toRS0VWtK9vc0OPGzPQCb4loJFQYAYAur3kHV+2NffOv lVVDiYNAqGPqqSvQZu5GSESrLAe2qFat1wCxlx20U2Erg7VdChuDOxSJIakw1iwUi W4qAy+Q219yIjt4l1w== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.228.125]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MDQeK-1uaU0F2cRK-00CS18 for ; Thu, 19 Jun 2025 16:46:57 +0200 Date: Thu, 19 Jun 2025 14:46:08 +0000 From: Gary Jennejohn To: freebsd-current@FreeBSD.org Subject: Using SCHED_4BSD now leads to a panic during kernel boot Message-ID: <20250619164608.25ef163b@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.20.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) 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-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:15jPeCb8+fGhWbpuPfN4pT4+kIvrRlr9zPg6Aw0MjfXH1xrJb6c qAW3feqq+jH4z43J+BM5cxuhyWtSXUNSo1t0Fq8p2zEKZGgZqes8ooL4mmEvpeINnLw/C3/ He+mjszFohNgUSHjkhjLK+3qRk2Hg3bszM9C3lVGPOzhCzZVAc/D0aJoAeANsrzY+c7uQ1B a2TnZy8Zbn0X3qPGPsZng== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:QfOvqbOxePU=;PtrQl18RDnjoZKLwTM4a32ix//T G+B9/nL0MnI4vlwq2CapD/eBWQjaKfspe7lKZ3hlab/wp4YGR+3dprvNPD0je6eR4U7Lfcey8 ELcj0/gA3pfPhRwnSXkIzQn5wx9Jh3TM1KWEuw6/r96ymIxPfFBEU2wqVUf8cy4FA9yS+nI9L f8KHLhuiOyJlQHE4Iqu5QqEaAoJ+26MpwwV23xum+jItqi38eQphINOyiBzznfCR1YXrGEkVn 2up72vyeXIh4EocF+OtH0v5iSAtK64905hVXWeeN95mF2kzPCgcm2EhBszgOduvDxoo+QXR3N lHMa+KF7uN44rUtcxy7cSzni4k5/LNiQOg9S+PM6iGDfCH4HtC/fhBRbbRPraDTOY7MFgzv6I ZOrOAYzk77H+VBKp+1QMAo1DK8pRzKWGuylvcRHbLGTH0gGVgMs1JUA+QZIC1rRGtZLHMyaOZ 4fdY+FuAoDYZQd1G9Z9pWJJYNxL6kE0F3WaOYEvCf0aSLsvFOoyQ4gU+3mg1NQ+Prf23HFniK HwrSBRR98NKBqtP6jBKW3hEILabvMIj4/3zGQJSle8+Q2ljhZ8aDD128WytFhHli3oEyQKY7g oYvB+IHYz1uEmXnbmwWT4L3u4RC7rVrzcZh2vrJvCyjBFTR4AOr9N8utzYrUwobCKT9zm7PPT W5fjyjZhT/wIIE93D3taRxNGtc8XlsWlo6lovZnoP+bFqZdiA7/xL3eXGQeSsXEgzoOltTVpZ 7YU/BYiyQ//ezKDTE28XjwAVyeWLv0oLw6mfbJp4CO/lTA4dgpdf/S6BwgJPvJw813kJPd7fm SJnBBnFQH+SmSm9I7pRAssKM7e6H7ldkcwSZ0/5Q1UBnoIyUvLToAQmO3wVUeE5sGeO61o7ux rZj9XR5jkgJypA/cerAEnXDuTd8IcCovvGTPt/W16zmK8UmfJbRDJUWWdnt8gxMBJ1ZKoUd8k sFRaguu0U53SPnMuBzo/M9HNtxzD3N0cTGpieRydN4w+RDsxhlL3IyawGjJrxNVBugyMiEEoJ muQ1AUYb6CgFZUuC7X1JeR4f+p34Fkiv/i8hkdhcb3i4sLqnYesWl4Xg8tptkse2DdNLDmsB4 cDmSGmSb7tnRZTW6CA9NX9xRiM0o56KVeEikxcNRgLNgm1+VgjhV0A98f9/ZbpBOQ1TMCn6vt VNs73Xbt0kPWSHsj8c0SH7ZrGqPBeJO9J/UPShpXm9pTdxC1T3AkV1/TClNNhuP9HHamcseUO itlqCplW9gWYKuuRGZv5t/W8PARHGUBYI/6gCsDuDmylFLCNRnZcgT+/9kvgffhM9PFBBZNI0 d+QDgwGH8AZPW9L3c0+WtsGQdenQj28meMRkhTjTEQ5CjOU+ge59S9HH1IXARPHIp5bbK0mG7 LmAMwvhKYa2gibi+Tg6g5Fw/ZxWH0ps/h8O991Msrps7evUBm/Jm1eVtVWrMudHg8zBReV+06 CyJ4r3hlQKytL7BMmHc5gH3xuAzD+58a0tMAsz6ISbZz0092EZIcnIN7ufTE2S7BvFRJWAWQ/ Qg5DVhMPiW3/gxwmH6laE1ycIHXNezNwKPWOBRaJtiO2IZCY3DwZTMWhvgZx/l6Jw9MlVaCJl tEGI4l3UG7hB/nPOozyAVmv1om+80gV4veQ8IkvhdF5EArO/IWXhyG03Z979Vttxuo4H/4S0n fkMpC5TwCCtshIEXj0O70gS358sZ7k23w1eMZ56ByYOgCTbVu4AkWD1vzxsDlX7R/rNAAXdXK xk0nGXbizgdDa/o3jkhlTxghrh7IP7ISuPJ0s3fqlEHtbqKG5MYKdSbf0uGu3ASqyNiXwLN4M yOWjzqYnvi9NMTvGOsXoyeX1CrFFw6z5O1MVepENovmWfTgZFkZ9dSnWCqQQpjIBy7118DydD 4AACwdKlBamiqhgZCtgCpfljh/IInBMNUnQxKq/Q1gHKa2uAlN/DVNj6cDoDYwdSWqq3RswwA 69OsHUPzBjM2qvH2sm0deTAE+3qEvEt/VNSqGUxbHiQ+YY85Pz+gJFbOC99eCS0bwVEr6FrUu MlPSO1jbaQ9ByN7N00sUrqr9jyppfQCdLAvHgkZRV75TpDIaOu7OB+tzd7gcsbTZB8a+QSUx+ TiHi5l8STTnaIYUmUL35iISt7Vc1bChfV4D4hQ4iae2NVzm7vTp2qRTDFZcGSRTBsNdSmlDBD 5oOAxRFr4bFQhZvVF6IskiHhEBPceNrvDA/e1Giq5PXVOGmShddPejplRczp9jy4GKkOMsxxk CrOjpMMNlNV3TJYdo5nV3kkRQlrb8a3UNKMZ+noJYTaEq/l4nV4y1TNRCFg1amIN4+SnHFnnU 2nTuhDxMjz5yfPCb/zY0Lfyg2HakRqrmgPtFJd7JS66ryv3iDvbKP9TIROtla9iTTXROaZeyS zG7YREBAQijF8ayYYcsFRbpvEiz08CZTtT2aJbNBp0u0m/CrIda8AI4lBvd4q9XqfFLaXWjuh NDoWaPHwimH3GwqIAZtyC4ARCCpgNocwX7P8/GQXd3Z9zV2mTpP6fAhSERddWFl7TICIs1cds I0NW5i5uKu9Jzga3s9e9bEkCE3D0x99HwPHdylcdLuD9LX/z0VkTWlKZWm5+tONQ953fGwHzi 2+HWzcKr/m61CbWPy0b6Lh8nTxLFRBCzhY10iDawyIXVbQq0pSNLwOehtbeM0CDwNFIAynHIZ dDnN9J4Qcr06kyi/mAGBU0vPNDOytiDvFHMfjIqPMhSnX0hLNDGDXJh5oVy5nubq1/EgLoxg0 HaRIj4puke2DXTCyIAlociiK18ez8Xws6Ryg5c1h69NE+SK+OG4aFtOTJV6QBacw0wmZ6f7TF 2HH4Kyzdhurs0COzWJ9/Yxaafoaipqld+dZoTmP5HoIucPxV+ojj6btl+zTbWB7XE+IkZTKNg HOnrDbdlNRh5C4M5v36R6fPWOKfM23ULFvxhkqM4z1RvL+Q7TsiroUE2QmWTm6EX3Gvj0yAnY Y/5l1v5X7holXaUu87WtekancBy04gFe3788Tx8p5LQeO5GsTTF/N6TMR/+izetPi31L7494Y 9lXC+zxM0CpOzb7Pe5flj1n6YJnRz6VLf2aBhUucI0QPohBMUuvutFIfPvEpg1SXO3YXhMLz8 h5gYp3hKr1hNNn9JwSbbaniycg/Ql1YIVaKwy0bWppgFxAGe9UseNlrme7A/RKwN7nprMpETv /10zcq8lNJ7hInzZJAXapeGOILM4XBK4BfOsaeG7b2EE0GcrpYCS4R67PmPsr7tJJbpU= X-Spamd-Result: default: False [1.90 / 15.00]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_SPAM_SHORT(1.00)[0.997]; DMARC_POLICY_ALLOW(-0.50)[gmx.de,quarantine]; R_DKIM_ALLOW(-0.20)[gmx.de:s=s31663417]; R_SPF_ALLOW(-0.20)[+a:mout.gmx.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[212.227.15.18:from]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[212.227.15.18:from]; FREEMAIL_REPLYTO(0.00)[gmx.de]; FREEMAIL_ENVFROM(0.00)[gmx.de]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[gmx.de]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; REPLYTO_DOM_NEQ_TO_DOM(0.00)[]; DKIM_TRACE(0.00)[gmx.de:+]; HAS_REPLYTO(0.00)[garyj@gmx.de]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@FreeBSD.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bNNjb4RxNz3wD2 X-Spamd-Bar: + I downloaded the latest HEAD sources today and compiled world and kernel. I use SCHED_4BSD as my scheduler and that results in a panic during the kernel boot. Here's the text from the panic copied from a photo: panic: runq_findq(): No thread on non-empty queue with idx=3D43 cpuid =3D 13 time =3D 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00d6c4= ee30 vpanic() at vpanic+0xff/frame 0xfffffe00d6c4ee60 panic() at panic+0x43/frame 0xfffffe00d6c4eec0 runq_not_empty() at runq_not_empty+0x72/frame 0xfffffe00d6c4eed0 sched_idletd() at sched_idletd+0x7c/frame 0xfffffe00d6c4eef0 fork_exit() at fork_exit+0x82/frame 0xfffffe00d6c4ef30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00d6c4ef30 =2D-- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- KDB: enter: panic [ thread pid 11 tid 100016 ] NOTE that I didn't get a crash dump. However, if I enable SCHED_ULE everything works as expected. So, it's pretty obvious that something is missing in the SCHED_4BSD code which is causing the panic, and it would be good if it could be identified and fixed. =2D-=20 Gary Jennejohn From nobody Thu Jun 19 15:20:33 2025 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 4bNPSR51nzz5ypHx for ; Thu, 19 Jun 2025 15:20:39 +0000 (UTC) (envelope-from olce@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bNPSR3xh2z4BKp; Thu, 19 Jun 2025 15:20:39 +0000 (UTC) (envelope-from olce@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750346439; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zPZeYSGI9+MAPIdomTCoreAav7HPk/sec14aCf01n7Y=; b=SefZykoHG7JGNxEITS6VB7yru93FVIEzx3HhdHGXZQqpU+AIh+heY1tkQm3enTn618hvk/ cSA+CBF09rLXZU1ltroOb8yH79XRh7viDTUadd7Dhi1HQtzNNwawtG8xvfO6PCf4Myz+X6 eUCkyqz+TsnGP4nnBYJQtYngUwn3bjxBWFeAgCxoCjjKLUEBwv++/pGTI2JyJ1elkSu4yD bsP8LKPGIpQlZyC/T/CeQbdqTjpHZwSYq7G9UFqVYdsu2rhq6YjAu5iqnCfjd5Ls9Kf8ZK HXFtv7YOXS9m7YiGTOHkdx1SPvshT7PXy2rnL8BX3YFUt1IdPRRCoXyzLHmIbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750346439; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zPZeYSGI9+MAPIdomTCoreAav7HPk/sec14aCf01n7Y=; b=iyklmmF5rH9W4fpM5EUZQKY8uKuiQRk6KvpaJDXyW2sc4GCh01jiC9bV3NHsx2/9VsizBN ZA+vpMLhEcAeP4/E2xcNTcMgfct/ZbNQJMf/6Vp5ZWtzRb8qNxgLjEsn9TtIT+LOcOL8ou KgAZGVN+IPgg0u1jx8TnrixY24gjUc+XDW9xYQA5qa90o82zINHeIMen9tOlJQBrzEUPRZ PrXEUwUx2PKzGvKp8GMPpJIxtgp1zSwEBcTCiXQjFcxgjmzq02LaUuSkiIanEAU50sApng SAzEzgz9myQvr20LDW2Qbm0Tjn58BUkOfHLyyBuDlTB4wEQtl6Fj/O5cKZQjWg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1750346439; a=rsa-sha256; cv=none; b=bpZyRGLHW6gmEbByv8msXjJXtk405cZzhZbPBUyAHTi3oTbFlRK785FKUxfgFLtfotL0QE B35gOMBmxgs5Qjrfro+qXJpYvO3rKwGS6Ii8e5aCwV2hNPmsG7N1SOC28ELBcAoCzgYFGf v/SVjluGFU35Fc4HXGMFaJcJeETYMHqJpupLi2V0DKi8KoldlCDCpqtvBpXXq/uzuebOhZ WG8ZV64lqNMk6xKaj+pPRmPBVvrkGCvqHp/lvwh9/6yb2yhhdSugkrohKPLc8K9rCVHyub f2p1LyXZpGThj2RA+xjWdnzL+cJYROKO6NT/CxmG4L2pR0wZUB3lcpQFM9EWdA== Received: from francois.localnet (unknown [208.72.125.4]) (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) (Authenticated sender: olce/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bNPSR2p6Tz1L5Q; Thu, 19 Jun 2025 15:20:39 +0000 (UTC) (envelope-from olce@freebsd.org) From: Olivier Certner To: garyj@gmx.de Cc: freebsd-current@freebsd.org Subject: Re: Using SCHED_4BSD now leads to a panic during kernel boot Date: Thu, 19 Jun 2025 11:20:33 -0400 Message-ID: <54746394.J2yNMGElB9@francois> Organization: FreeBSD In-Reply-To: <20250619164608.25ef163b@ernst.home> References: <20250619164608.25ef163b@ernst.home> 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: multipart/signed; boundary="nextPart8463195.G18vQ0XA4d"; micalg="pgp-sha384"; protocol="application/pgp-signature" --nextPart8463195.G18vQ0XA4d Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Olivier Certner To: garyj@gmx.de Cc: freebsd-current@freebsd.org Subject: Re: Using SCHED_4BSD now leads to a panic during kernel boot Date: Thu, 19 Jun 2025 11:20:33 -0400 Message-ID: <54746394.J2yNMGElB9@francois> Organization: FreeBSD In-Reply-To: <20250619164608.25ef163b@ernst.home> References: <20250619164608.25ef163b@ernst.home> MIME-Version: 1.0 > I downloaded the latest HEAD sources today and compiled world and kernel. > > I use SCHED_4BSD as my scheduler and that results in a panic during > the kernel boot. Strange. Looking into it. Thanks and regards. -- Olivier Certner --nextPart8463195.G18vQ0XA4d Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCQAdFiEEmNCxHjkosai0LYIujKEwQJceJicFAmhUKsEACgkQjKEwQJce JiezjQ/+L0G4qLx7isCJrBY0uDkmnTeifEyVoqjXc3CIxsOdljCqDlZRuZrCK7l0 0/kdR780NaVlBg31MO3QgA2z62U9wxCj/zYQWXlfefSapLK7NUhlUOsRZCaMTs4R /+JA8FzVmfxmMYTUb8I/Iu7mJvKpShUQLFBzcpKJdoqo/FKiL8D4KKqRPJK1dBz8 Zyxegq57nvDmyDfcOzuqgvjpo7WwIdmcg7MQN3qeklCHDm6Ri8zfVXKRTKHKJ8oh x/8JoIPe2BwUVKfR3tZsWEbYPx5rOoR9LIKJ8qlOmO25cZN7g7U9UPx7wt5aetxr a2YjnRtVBefahluvsREuKEK5IuVvigEp76DDH/jLJwJzZUVewdWkLj3Gjblk1E+S FI0tAqfhPScODfJ+NvVOEeCo2ykOl30RrJ16DzdFE1ckJu/P89jbD7NcG1L3AI+S 83WU+Ar1jMH9NbaMsXszWjJhgEWFiBWm9/9vKXDihJzgy4AGlXBq6G/FPihsoVNg pPP4B5bfbLRgCLAITnWdbBlV8gRUutuIOIYgyEsWrxJ3edGFvxoHkWeQYizEE7hU JWxgTXMqxA8Q0uazkVyf9IZHC8nF35+RXgukBerLJyVvAK4NOX+DP9ANG0fSsdU0 ZjHvHPSsi9IYgS73VHq7bBZYm+LbMDonGmcoFZ+qqIP2BjQCRxM= =gDQE -----END PGP SIGNATURE----- --nextPart8463195.G18vQ0XA4d-- From nobody Fri Jun 20 02:44:01 2025 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 4bNhd64K3Dz5yM91 for ; Fri, 20 Jun 2025 02:44:10 +0000 (UTC) (envelope-from olce@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bNhd62cJJz3W7H for ; Fri, 20 Jun 2025 02:44:10 +0000 (UTC) (envelope-from olce@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750387450; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wTrRGp4q3Un1ianWeXqprvR6mZvVkhsNZmRWQPtEp1M=; b=nxQUsaomo2zqQ/WwRZlVTu6hhZWwh2C2Fvja+JogUnWF6UGymCrc62hXa0R2tHfnxJybqX d7pb8TgWfo9V2cDvUt0OtzhDZKbY70J/vgWyXg5YT9J7IxYjv/HT1YHKQJmgaPw2GFM/U9 asONboaxDk7PIqKGzOwbPzFryQk3P4a2dpYjWGRRwQttCKDuwP7V3StFTyfCddA4ud2ErQ j/I7V61Uu9U9MjfNrebLbpqyij2rPty+5AGbAbd7+x/j852sn/T1fjTQWtD4f1y5R6XF9O mgzenSxhVgGJ7qbk7rIzI2jAGIEtEmX8boet87/i5uC1rG3FxaJDZM6z/Ks3wQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750387450; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wTrRGp4q3Un1ianWeXqprvR6mZvVkhsNZmRWQPtEp1M=; b=Uiv08BCwEAawHnssd65dYX8LZTGyJ58eLBkM2PNrrEVU3j6GGt2BUVWTvNyr0/sKiXfi4O vK6Ahq/Ku9bjrD+Tzq4cWFH8zdnl8+Xx+cXJFT9+gRs9FqTIS8UvOhRkxWryIxoubAxwQ4 yUNdyR578TasgA/ZiF8ck4EvJkNjSL7Ivf9d5E2GrvM2tF2MZ+qgVZlesfDGBQH5FoCs9N hCxT6O6ONJYDgvqKd/zBaqiasWlm94O0CjNE1A+jqgnRlX1N7kB3bmn1nEMAN6qCQQF0vj MpCfHYrqmGusgE71ORhwHbqYunbbN/2fqypBMQX8VKLRl7jdOw8vqV1gB2LkZg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1750387450; a=rsa-sha256; cv=none; b=aXicUKADtRBGv/G1aO3EnmHmkfx3wb2+MxlbNG/so76MWeR0LxDRi1qMym5vEAyl8+sp7d dzXeiX38pQHJYj5zqhwrs0Q1mxBwq7/iH7IeyFD9xfgA4eUMDI6KFi6m7riQNrkT0OuViI GJE7xtp8yaG2tcHNPz9LHuauVkhnQCKltEFW7uRAdTmp+baPlkBTmiKj995UgdQh5vQAoI GJCz8R5uFR35bxxtO6EHsiZILQDTDtXw1SomfvTFRfHPaEQiwyvetEUkAZLuUbvI4w+usI MLhrGsBF6fKrH3W1LW4FwUXvtmm6KznfGDJiIG78hcYkAEPpAHBtmiwDDufJhQ== Received: from francois.localnet (92-184-117-181.mobile.fr.orangecustomers.net [92.184.117.181]) (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) (Authenticated sender: olce/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bNhd55SNgz6Hv for ; Fri, 20 Jun 2025 02:44:09 +0000 (UTC) (envelope-from olce@freebsd.org) From: Olivier Certner To: freebsd-current@freebsd.org Subject: Re: Using SCHED_4BSD now leads to a panic during kernel boot Date: Thu, 19 Jun 2025 22:44:01 -0400 Message-ID: <5257554.7IPSAfTSoR@francois> Organization: FreeBSD In-Reply-To: <54746394.J2yNMGElB9@francois> References: <20250619164608.25ef163b@ernst.home> <54746394.J2yNMGElB9@francois> 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: multipart/signed; boundary="nextPart1944479.GETTdP9EZa"; micalg="pgp-sha384"; protocol="application/pgp-signature" --nextPart1944479.GETTdP9EZa Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Olivier Certner To: freebsd-current@freebsd.org Subject: Re: Using SCHED_4BSD now leads to a panic during kernel boot Date: Thu, 19 Jun 2025 22:44:01 -0400 Message-ID: <5257554.7IPSAfTSoR@francois> Organization: FreeBSD In-Reply-To: <54746394.J2yNMGElB9@francois> MIME-Version: 1.0 > > I use SCHED_4BSD as my scheduler and that results in a panic during > > the kernel boot. > > Strange. Looking into it. Panic comes in fact from a too stringent assertion. Apart from that, everything is working correctly and you should not have seen any problem on a non-debug build. I have just committed a fix that preserves the assertion in the exact cases it matters. Thanks and regards. -- Olivier Certner --nextPart1944479.GETTdP9EZa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCQAdFiEEmNCxHjkosai0LYIujKEwQJceJicFAmhUyvEACgkQjKEwQJce JidRjRAAsrGXVDQ3fkENDQeTmMOohY/OyNhbsJNTyGVhxtkIk61nPYUihKu1Kdc8 +4PjzLc2OXZFAE/MHRMnu8F357t7keqrfPZbY1DMJQFgkP+b7h2lSZcSd54IB84G Os0MjRlisbALRSB+MLNCbekoJ1JyI17eUK9NrzNVZh5G5LC3J3fP8fvElB/EadLr afIK1YIHiA4QAIBGPbVCO6lTG4KL2SIhsgEQjRsXoS0anSV8HKudWnM/f6hpmKM2 nzQnSL8sCFNO1xfblFkji3ac02yMeo964ba29eEhXQIT3Z3KGuF3jSwueN37lbTb HIzF1V/6x7RW4cNXulyRFyK/SPdGbwDtVhq1heOeXxsc77nwV6dLXQvnOpNK9FBS 1H2xkYYK3qKmYMlUc1i3oNu8KeD/UmrkmNBaeQafeRX6JUULU+aM/tBNoJ+IIb5y 3nXDpKvJKvmg1YmaUyfadZvZYlqgKxqG2VfnOP/vaoqXyJ6b+yQfBrSb9MoDEs5x 7X0l150tVf2QyE5JcqmSJCdvJJOEyQwDI+JEPQ+TfxExkTpARnqHUA4dQl4brl2H Qj/NEnznXPdndZsjuM0asluptK/ioWjnwLV3tABr+YfKIfsB1F6ZsBbRF6ORrlSb S7c7c/F0xtw6cRPz3NYLBdSvNL0p/j4ymlW1fkJn0TyIvHe64BM= =Mrn4 -----END PGP SIGNATURE----- --nextPart1944479.GETTdP9EZa-- From nobody Fri Jun 20 06:58:40 2025 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 4bNpHp5YPcz5ycfw for ; Fri, 20 Jun 2025 06:59:34 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (3072 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bNpHp1CRsz3DlT; Fri, 20 Jun 2025 06:59:33 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1750402770; x=1751007570; i=garyj@gmx.de; bh=WEWo6dfnMZSyehrrYYsRCooR1BRZUprz5a/H7x9TNYw=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:Message-ID:In-Reply-To: References:Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:cc:content-transfer-encoding: content-type:date:from:message-id:mime-version:reply-to:subject: to; b=WnBCZBohLdlvPGifp2PxB+jPA/4LdKZJQoGV5nWY3WF/GeHGTOsxAgc8fzWlt0Lg 7snuu5ul+PQqfwUsr4kM/W7N/vfEQiryggr/j2auQYeOtSSa6QkEqCKK0WFSz2VFj Yqmw/JSvUYp9NuwEMLHfW2PtF9G0ZsuT02nKGq1XMhuerjRhIrVt9u58KdDs0G4YO 8yhL9yFHVMV2ZCgEoCbNfIj2niv/US1fzqO7Y4raB7rSwljcYqADkomE279MiHx32 rC++NwvtLG5C16C8CmLOoBpb7vZIHCRY5qgonvObOjbyeZ12Q0Jux+NXe2AraqLLq pGVmbCzzsVdQNPXD4g== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.228.125]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MTiPv-1uKe1X1xV7-00SLhB; Fri, 20 Jun 2025 08:59:30 +0200 Date: Fri, 20 Jun 2025 06:58:40 +0000 From: Gary Jennejohn To: Olivier Certner Cc: freebsd-current@freebsd.org Subject: Re: Using SCHED_4BSD now leads to a panic during kernel boot Message-ID: <20250620085840.54231e87@ernst.home> In-Reply-To: <5257554.7IPSAfTSoR@francois> References: <20250619164608.25ef163b@ernst.home> <54746394.J2yNMGElB9@francois> <5257554.7IPSAfTSoR@francois> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.20.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) 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-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:46nnyl2KKgwyqEF/1aoxCPE+O4czBjqLZJCtZpjRQHoySlLRRsM ZD2v3Fs86WkfjpQ4Cfm7SxF3ZHr8QrH6vow32ZqW5DF7WhH08BtNLYBH7vorLOrTovqK5av CPfMZUFa6rRe+9Nlfa5ynsWBn90qHv3lLhnAy1w4K9Mf1ZBkcIEApOAERPn7r5KrZIo0Xlh D/qeTnp/dgUV0eGYSmpqw== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:r8X7pAt+IyY=;/BgGZWhh8k9e+i3ZcpixFbJetAZ nuINRVymJpXL/rmhPV2DkZMMjIf99SAbOD3jcG4VGpMiDHcAsKjqvT0jB2iJLzbXhJwSozc7f 1CwtpwANzAHP5S4ka0Y+bZKj19eLbebzeyDxLHWtL/4S/LdPt4vZjjCi8JkjN4NZ+hnawX3Kb 26dI6lcqNJ65c5DARG2FmwZG3zS4RMfWfYn8qsRZpOuFl6/1fm1gTIoDpt0WrNzeYqc3xv4R9 Ax3jpKJ+/GhD7MwgNW3tDtvdU3ytPm5YH3J+Ebitn9i3JvL6g51mTZJpGqQ/LVD6qvcF7P86H c3s7IS2LfDtvfOW3570W8z90gdtbI89kNOPEaCDPpuEGml2GvQzoVuQhlARD9ZALFf+u1LHza lInS+9p1/121Xd3VJ2FsDUlOMbhILeQvBnV8ViYfPxDTBKs51zB47EohVu5xBgFfP4+7th/tW QIgt3k4pASNqnZcJWShcHyh5/7EloINymbU15TK1DJDDPuKVCSDl+R3/UoVqJW39O0whbIXtF q2Ubz95KMCsP9/ITwwdEmVoZOLkgGwKbLaxbT6vp3rTGKmx0/k/qdBE39eyYBWnOve21pxaYD UK5ElHohVYbA85gpLKf3TI9zlxqWremHfIweQmrvwsFGbhtkZ0e6z7+nn7EnwWvNS2KG3+mOH 92mF/BUAwKmpG6DczosgDiKfeR3J/M3LXDfRyo0zYlAVHE8bjdEuuoL2Mxu5ERkA53gz7xXwy XceH5RK61M8jBv18WXTNz/5h8qFKDIQYzt3uMnTx6+cwox+nasGC48i2zm9IsGq8W4BE/HfVk mlR9nXxuMzCyYrDjVSO8lqvDb6DX6RdYjrWTyw4BBU2oPr11O39Ad6KuMvu7IJqKjpCCE6WFX bwMHMA0+bnUoQ84YK27JLVXvVVc+BZ8kv8dN/t/LtsbnQ5f2j+p/qfu198fn+y80pD1/7GE+N MZKkNQJpdkFw1KkdoROxtqdDxkjQ7ctY227rxn6RhmP6fIuSVPhPqflVqfYOmQN2bpobKvGQb 6s7Rk3cSF6jFdCTFw4eQHrWEkyYa4jFrZeIZEjd+tKLITgKWH/gg3AW0460OoGe+onBERwqHH CH9QkwV8DqXqujk2DySQE5S8U7T/ABP9mAk0nkhEgwJ95sObRxtsiIbX5toip0GlQpHVONAxw Vva1OgW7AXe1nl8HGqHNGaLzOXSogFbY6wheF6tY9zfDvb7bETO44TJUQOdABbGcCyWaaqx/E 62JEPLcuVNG02XQKcVRMTWKMaiH1Lo7R4nSG6zwJjjSlt7RjkxmR6TrJJE4xN4Qellrvn+fTs DvGJ5qF7AN0bPxqyf3y94P8nezMR0Hy5wDktDH/OfWBW8BzKUi/7bYYW985t+4p849Nd30u4z 5FFvIEkeEZfdg3fjru2/eRGrv5JC0y+PhtbcbK7ogfrbMlOKYFfPD4wSxrx/eVL7XW5Og8vtv R3Bf20HXOVQRZMSJ5GXcqXc1DJvMxCqxv40hGzHBGWJivTYJU0Pw1u20LRjZuwUNTle5W6h7a FtfVC06LOZwNXeNCr8fOAQFOgQXXh7spN/vn/OR2fSxNbwn6GnbCyFBJVcGaBoz57m6LzpJxY /0eCqCKdjksIVwtwA5bTiaTKTd0YrFgAPrH7fIdgjco1CXnoT8dg5A5Ui/7/r1YUeljNvHtJy cV7m3AzWb7ZySMp+w88zYlNVhyBtZPmnXb7aoMLsWhuumIePPNSYHT8Ek9b7D7oDsYGirWDXB QolZcZ5kQUn+sQ/dCUkor/9FcjOoEhqipGOFWijFK9P51KhsIhA8XK4r15x7QvCGPdt3pENPj TlMYGCX+7EPvq2yKvwLp0mLUV2jg1pCOoGdC6yxrcg/D6m2SGq6t50LtWv48BqwIzTNsCjk1L HgB/flkgFoll6OpQlFMDHzg79CLc3vHOAj5IMTSusnJ1Ns9BPVLiI2jAw2CHJRGyE29FzrrvZ YOBM2YBN3+zr2CDs/+KnrTMAbh65Yweui46N9vpyFMZmE3lL/N4sTXbZxAqY3OpCUjrCgUUU3 zJ+l2u6QfUeYXCPuX80Tu0xtD5tThMotsoqPAX1c3dTjisgzTEDATyQpOu5dWHD8yLRJifNSp MrvKXUeZAiECxJTV/3KTMvLV7Y7u3GmnQq+BKAKPqIq+Y9wqHaEHayX/+4+P/r+QRLaj6IxEZ a3/OZFwmWuLm6lkUEdsb0yzspq24yICLkb3CcOGAtlbdM61lykK9BB2R2jHaIzUAE42IFaQQt FxbS5zLxwFmLctZScM9lLJRPj3+PrTql83SwUzsmaLYxO8/0q1SnIdvd7Kk+0oMOttZSlg6vt FAPY3I0Pu8ESTAT6mtILeQtSg0StUXtOd+xctIN+s8/sesmUnVHitiN6dXtDa0YyBH1uuFDKb rWpw4KEysJ+adIyvlpSga9Vu5kgm+MYGXD5CEzBGvG6Xg3T9RzYOunZ6Vk0sklHsjvvMnzDRa TtiS+b2El0EwO3Cly0Ow6Q9VuVR8hTEub/w3ZpaTksI8dAuzXjthnCXKTMDXhnCoLLXj9hPgY JIOkaaXWCHNDXE0y+3TAZ19ypxZvQXSuWkAogdoUNk434tXPlCoop2hti2YOy+fznudVV2kZW GqnNu1FwFCs3e/Em21MqyLGh3HzDvrRa6xOE+3wR5bp4g4DC4Db85v8n3CsVxKJHmN7Xj1deY T8iZylAyVrKXUFTWfMUcXcemTLH2XP83VW63kCgFBSDCd84zDJ82QEilm67PI2rZBo+X4MM9S 1mruFe5Bge0NPy73nTu155WfrSX2ZHENsFzDfjJZJAhCbSIEUuFsAynaRXm3bwZdcaZYe3zq5 MzHbDfOnemTZ+eVYbqqqfzy7rQRADpM3qNJwJhBKCcnzuU1o0lcL4q4CzthbrkQqjpTbtuH2K 1Tw0aWTLCMuZjhojxyuo921DtOx7yGWQxJ62yAqzFVs6Sl6JE0K1GQXVq5Qs7aQ4/8JNiXtuB ccaYt20OOj3AQO2jfryXx3+Ew5Lc5VkkZuAOVqpWWaOH9sFKHhwf/j7DoTP8U3pfb0iQTI3nG uhn7joK3JjVw0GRJjCpDHqn+NYz1K7G5wg+GQiO099goRG0/K74EOiUHe1ROR1iWylYJdq/3p HPTSjRJ583sM09bIltf5OmferWZU60/3suZjvbcgoXNHGqpBc0bW3a1DNPflinVnnKIcTqPqj wNpbsjuSZM0NyzJ8jrrTWiW2cZXMJpkaXo17vQfLboQeF4FZ2vjh1MhMTNzgLRsKrWRg= X-Rspamd-Queue-Id: 4bNpHp1CRsz3DlT X-Spamd-Bar: ---- 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:8560, ipnet:212.227.0.0/16, country:DE] On Thu, 19 Jun 2025 22:44:01 -0400 Olivier Certner wrote: > > > I use SCHED_4BSD as my scheduler and that results in a panic during > > > the kernel boot. =20 > >=20 > > Strange. Looking into it. =20 >=20 > Panic comes in fact from a too stringent assertion. Apart from that, > everything is working correctly and you should not have seen any > problem on a non-debug build. >=20 > I have just committed a fix that preserves the assertion in the exact > cases it matters. >=20 > Thanks and regards. >=20 Yes, everything is now working with SCHED_4BSD. My custom kernel config file is full of debug options. Thanks to you and regards! =2D-=20 Gary Jennejohn From nobody Sat Jun 21 15:49:13 2025 X-Original-To: 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 4bPf0k02dKz5ygjw for ; Sat, 21 Jun 2025 15:49:26 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (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 ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bPf0j0Pfkz3PHP for ; Sat, 21 Jun 2025 15:49:24 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zabbadoz.net header.s=20240622 header.b=S0oitjLu; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2003:a:140a:2200:6:594:fffe:19 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net; dmarc=pass (policy=none) header.from=zabbadoz.net Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 62B41A64805 for ; Sat, 21 Jun 2025 15:49:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=zabbadoz.net; s=20240622; t=1750520954; bh=8n2XdBqrYSemAqDN/keZks7QrNSW1LbvLWkdz8NHqZg=; h=Date:From:To:Subject; b=S0oitjLurOu0/TpkwJyb9rYU4/FznwDa8ppDrJOdXApfnis1Y0vra/QgIdFzAjs+0 CoIkcZcHnn1BIjUXN9Ah0XWvfZy5T0EP1+0ngkZVWh9/sqZgontiPf6Ir/NHTa4+b2 KYFBKx9Jh0Vsi3Z9V8hoa8cVM4FF4/7cdl8ac5sivuclmjDRJ79zjSyCZt6y8kuxVg Hs+JgsUymw8NqmtU8t/yFv2C/mzxuLGtmWx/BAO/MgG/AWutTstxi22HsMm5V5dRH1 AjP1CKTx4zjnpmYho7/VOGf+qPATnqk9SIjcCv3c/XQZN1I8HEgK0AqUhgNbJYuivY iWeIKDa/2gCTEaCY4byAvDS9K25VPirsF0ngJBlSXXjtAd6zRVbqcbA8UHW4tBhpmD Lk/1FKHpk9hhOeC6KXaeFf4IEJudT5iLqSQO4eMR5samwTgS18TvIgmvPRDegfpYZb Nfv3lpLKtoiiQZgqcJ+6yeXH1DKhisdknAchY9q3UITdY7cnEFEP/+5lHTSJIHB8os XM1Ovpa2KCrx9HLlef19r/wO9efVT+jTCu0N0ruXMGrOrI81l6gsi8AXs4aC3Ow/R5 q8O74T46k997FOt7y0/o5oG1d9kAcT9xylnv3S+cdhL3ug51+xiKKCHokkDbmKO0Aw DZsknGc5Sbcey7nNL1QIk+gA= Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 565F82D029E0 for ; Sat, 21 Jun 2025 15:49:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id HeIsASPG06QH for ; Sat, 21 Jun 2025 15:49:14 +0000 (UTC) Received: from strong-rtwn0.sbone.de (strong-rtwn0.sbone.de [IPv6:fde9:577b:c1a9:4902:3e64:cfff:fe55:bc80]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id ED4192D029D8 for ; Sat, 21 Jun 2025 15:49:13 +0000 (UTC) Date: Sat, 21 Jun 2025 15:49:13 +0000 (UTC) From: "Bjoern A. Zeeb" To: current@freebsd.org Subject: regression: memory issues on main/arm64 over sched/runq changes Message-ID: <43005447-2rq0-6nn2-pnr5-4939s112npr4@yvfgf.mnoonqbm.arg> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 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; format=flowed; charset=US-ASCII X-Spamd-Result: default: False [-3.97 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.995]; NEURAL_HAM_MEDIUM(-0.97)[-0.974]; DMARC_POLICY_ALLOW(-0.50)[zabbadoz.net,none]; R_DKIM_ALLOW(-0.20)[zabbadoz.net:s=20240622]; R_SPF_ALLOW(-0.20)[+ip6:2003:a:140a:2200:6:594:fffe:19]; MIME_GOOD(-0.10)[text/plain]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3320, ipnet:2003::/19, country:DE]; RCVD_COUNT_THREE(0.00)[4]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[zabbadoz.net:+] X-Rspamd-Queue-Id: 4bPf0j0Pfkz3PHP X-Spamd-Bar: --- Hi, it's too early for stab-week but ... I had interfave groups ("all") disappear from the interface between inteerface creation and ifconfig prints during rc stage: if7: XXXXXXXXXXXXXXXXXXXXXXXXXXX-BZ if_getgroup:1647: ifgl 0xffffa080011aec90, ifgl_group 0, ifg_group 0 panic: vm_fault failed: 0xffff0000005e19c8 error 1 cpuid = 0 time = 8 KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x38 vpanic() at vpanic+0x1a0 panic() at panic+0x48 data_abort() at data_abort+0x28c handle_el1h_sync() at handle_el1h_sync+0x18 --- exception, esr 0x96000004 strlcpy() at strlcpy+0x20 ifhwioctl() at ifhwioctl+0x998 ifioctl() at ifioctl+0x8bc kern_ioctl() at kern_ioctl+0x2e4 sys_ioctl() at sys_ioctl+0x140 do_el0_sync() at do_el0_sync+0x618 handle_el0_sync() at handle_el0_sync+0x4c --- exception, esr 0x56000000 KDB: enter: panic [ thread pid 635 tid 100249 ] Stopped at kdb_enter+0x48: str xzr, [x19, #2432] I intrumented the kernel and could not find any deletions. It was more strange given the machine has 10 physical interfaces + lo and only for #7 and #8 it happened. I added guards to the struct and that did not reveal any memory corruption. Added a loop right at the end of if_addgroup() to make sure the list was coherent and it was (incl. lo which has two groups). Then I started over-allocating the structs (size * 3) for ifgl and ifg and put the actual value in the middle. That worked and the two guard structs showed no sign of memory corruptions. So the larger allocation apparently helped or changed timing (which the printfs had not). Then I undid the changes and backed out to b93161a7e38d and that works just fine. Went to c29459f901dc which shows the problem and panics again. Reduced it to eebc148f25c3. So it's in the range of: % git log --oneline b93161a7e38d..eebc148f25c3 eebc148f25c3 sched_4bsd: ESTCPULIM(): Allow any value in the timeshare range 51a4ae05abe6 sched_4bsd: Remove RQ_PPQ from ESTCPULIM()'s formula a454ff6b0440 sched_4bsd: Move ESTCPULIM() after its macro dependencies a33225efb4bc sched_ule: Sanitize CPU's use and priority computations, and ticks storage 6792f3411f6d sched_ule: Recover previous nice and anti-starvation behaviors dee257c28d93 sched: Internal priority ranges: Reduce kernel, increase timeshare d710acecc00f runq: Add copyright 055b5b5f850d runq: Restrict to kernel only a2d1c3bc2bb4 epoch_test: Assign different priorities using offset 1 b2a9ee2a72ea runq: Remove userland references to RQ_PPQ in rtprio contexts e3a4b989d7f7 runq: Bump __FreeBSD_version after switching to 256 levels af8de65ef23e runq: Switch to 256 levels fd141584cf89 zfs: spa: ZIO_TASKQ_ISSUE: Use symbolic priority 8ecc41918066 Internal scheduling priorities: Always use symbolic ones baecdea10eb5 sched_ule: Use a single runqueue per CPU fdf31d274769 sched_ule: runq_steal_from(): Suppress first thread special case f4be333bc567 sched_ule: Re-implement stealing on top of runq common-code 9c3f4682bb90 runq: New runq_findq(), common low-level search implementation a31193172cb9 runq: New function runq_is_queue_empty(); Use it in ULE 757bab06fb59 runq: Tidy up and rename runq_setbit() and runq_clrbit() de78657a3aef runq: runq_check(): Re-implement on top of runq_findq() 439dc920f2d8 runq: Revamp runq_find*(), new runq_find_range() 200fc93dace7 runq: Re-order functions more logically 7e2502e3dec9 runq: More macros; Better and more consistent naming 57540a0666f6 runq: Clarity and style pass a11926f2a5f0 runq: API tidy up: 'pri' => 'idx', 'idx' as int, remove runq_remove_idx() 28b54827f5c1 runq: Hide function prototypes under _KERNEL c21c24adde98 runq: More selective includes of to reduce pollution 2fefe2c88b31 runq: Deduce most parameters, remove machine headers I do not know if it's feasible or doable to bi-sect those chanes further? /bz -- Bjoern A. Zeeb r15:7 From nobody Sat Jun 21 20:04:52 2025 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 4bPlgj5qBqz5ywwf for ; Sat, 21 Jun 2025 20:05:05 +0000 (UTC) (envelope-from olce@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bPlgj5CcYz3gWr; Sat, 21 Jun 2025 20:05:05 +0000 (UTC) (envelope-from olce@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750536305; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1vw3Movd/lwFhwrLfLVM3xUu7O/NDYFeNGhgIY7/CC4=; b=B1QgC7/W3veQdov8UGnWMtWpxgMVnwb6j5JN9+30dlqBDcs8Zdb05v7nKhpDUvPpPshxQF ff5Xsx6g/jPOW5UfY9G8xi9RKQ/E16RTCq570WIQM5aTlnNAi7jx9kUeaV+Qbghh1+QUjG 0DD0h0fZdgt/AkXrP9SDhHztlSd8nLTcCMbIPnkeYR3Bp0bymU2XEsRIqEJZ4z4omTXI/L GCVHjp3hSIDy9MvHv+803RCPftXhwUH6Dlpi/DuClpAaHVD8PHctDJmpILTuLed3Xe0w0/ 1ZEGynFdDCLK7q1jlNkJIBzdpmGG4gPAGTr+FZbnpl0iX0SG5Cm+hzL15drx/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750536305; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1vw3Movd/lwFhwrLfLVM3xUu7O/NDYFeNGhgIY7/CC4=; b=jeh77Cy3vQI5o1x/ELY5BMe4CEYdVM5Ki1rNQpmVckFnNn5e/BKp0Ai3zXnmpADUmxz3P4 rB7MhAu2mLsUauV0ZKHn3CwIZSfnt47Rs9QCRdYl71kmBiomHEG1Q2ndy/mq4PumCxOLUE RXDBqhcSRu0sGjtR8nAv6igp7QSmHiF8MgF/XNzmw9oS6aOpbDQjvIqJDGF3uHeU4bFJtS Z5T0mUv+aAFs8VljIveJ55xD57aVatdhF6uMLeY2q6gb74iWBCQGn45305ChqKey36giVI at8Oe7FQzU16o1Hkt265DzIO7tbf2diUxGugubKOUnHF9GDna7ro0NS8IZfAww== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1750536305; a=rsa-sha256; cv=none; b=fjCy9fE2ReGK1qiLwPMPBGRBMCdq4kMML/dI57HnzWFChCGEHNG4cAg+pw3gnofAPRxIKR bCWE5S2FZVWC7r43lclKGVpRclUkrh59GL2SO+VsJai3QJytFsHa6t+IfLXxkzDHX+i90w Rud85YsSOjjHuk+Ibc7bGIN41wb90BOuNIXLd79OMm0EeHxI5MA3IVOLWOfx5auZdCmHz8 vFgtAVzxm6y/bcpFuDpouK1QWOXV8oCEkbMWssjiJ31gKoc4HlN2DXg1tv499utqbomDkY a+LljeN2pAuvX6hq6cqrJf+lvRp+reFBR/zIBHsDjnNYqbpYJuRCLDk4ZgiewA== Received: from francois.localnet (aclermont-ferrand-653-1-222-123.w90-14.abo.wanadoo.fr [90.14.66.123]) (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) (Authenticated sender: olce/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4bPlgj21wLz26L; Sat, 21 Jun 2025 20:05:05 +0000 (UTC) (envelope-from olce@freebsd.org) From: Olivier Certner To: "Bjoern A. Zeeb" Cc: freebsd-current@freebsd.org Subject: Re: regression: memory issues on main/arm64 over sched/runq changes Date: Sat, 21 Jun 2025 16:04:52 -0400 Message-ID: <2563206.rlboQYEQCB@francois> Organization: FreeBSD In-Reply-To: <43005447-2rq0-6nn2-pnr5-4939s112npr4@yvfgf.mnoonqbm.arg> References: <43005447-2rq0-6nn2-pnr5-4939s112npr4@yvfgf.mnoonqbm.arg> 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: multipart/signed; boundary="nextPart5750140.2f8PWJG3B8"; micalg="pgp-sha384"; protocol="application/pgp-signature" --nextPart5750140.2f8PWJG3B8 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Olivier Certner To: "Bjoern A. Zeeb" Cc: freebsd-current@freebsd.org Date: Sat, 21 Jun 2025 16:04:52 -0400 Message-ID: <2563206.rlboQYEQCB@francois> Organization: FreeBSD In-Reply-To: <43005447-2rq0-6nn2-pnr5-4939s112npr4@yvfgf.mnoonqbm.arg> References: <43005447-2rq0-6nn2-pnr5-4939s112npr4@yvfgf.mnoonqbm.arg> MIME-Version: 1.0 Hi Bjoern, Given the amount of analysis and test that went into the runq/scheduler commits, a priori it is extremely unlikely there's any problem with them (assuming you're using ULE). Additionally, the scheduler never does memory allocations except at initialization. > (testing/fiddling reports) Assuming the commits you listed are actually the cause of the change in behavior, what you're likely observing is a race condition exposed by slightly changed execution orderings/thread selection for timesharing threads. Since you said you observe no deletions, this may be a race due to the list being observed while being added to. Actually, skimming at the code of if_addgroup() and if_getgroup(), I suspect some barriers are missing. Out of caution, are you absolutely sure you've so far bisected without any local change? > I do not know if it's feasible or doable to bi-sect those chanes further? All these commits are independent, and you can bisect them as usual. Actually, it would be great if you can do so, as apparently the problem you're having is not completely deterministic, involves interface groups which I'm not familiar with, and personally I won't be able to spend a significant amount of time on it until Monday. If you do so, my bet is the outcome will be baecdea10eb5 or af8de65ef23e (more likely), which would be one more hint at what I've just said above. Even better, if something like fdf31d274769 comes out, that would be an actual proof of a race. Most other changes should never come out, and if they do may invalidate what I've said above. So, if you have the occasion, I would grateful if you can bisect and report. Thanks and regards. -- Olivier Certner --nextPart5750140.2f8PWJG3B8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCQAdFiEEmNCxHjkosai0LYIujKEwQJceJicFAmhXEGQACgkQjKEwQJce JifVVRAAkOwMcx3omahxQxhY4YLtnLpD1dtJ6vau4wJbK+ADz5D2vVimmhC68Gxs TQFH2DcV3sFfQGqak3Dvt7xmccfS2ay8mjIOIxgDExebdMzoITtSW6/Vjp24l5IO sXaPDCiaEWtm6LQbNAi24EEYPelFi90+G9o6G35ETbmRm8ZaKnq+LZPnPvwSCZFI 3i9vRyPAnmWTAywasZzuX+HqTrWHBMTrAAfxzpVAav6VT+m/Gn/Ngng2o+6ehqxi O6jmenumARRPsTyk31t1Zt/O5HcXQQ7Xdt9n92cybDSbJxuMbnqhDqF1TpgVPr1y NV70fi5ftsZmsh8i/VxcBr4wjNWruX1N41ExuyY+KJoUakiWq9SNZ1BRGjtHeVrl pTdARNaGT9fkEyfEP8TkJaJkBQGQw1Jr85GfDFgasNnNQylgvrFPG9zw8isN4Jkj 6lbkoY0aqafn/obzU+9v5o1eVVFRzIE+H18Uv3ZW/aMTAMmNolqbcgnC5oOgQb+5 AoAGFpQcOxJK2nXdtFZzQUm/y+ctVjDuGjdQ0HZ5AV72lvc1bBxLYaufB3uNe5uy xA7BxPpluNoYpNxv0n/9tHAbgZeeWhOvNAltQtnJwnkg9yoaMq6jhpD4e93xpVaJ wq7fIGbATQl4iBXK+KdXAlPSr3iN0FDpLjWouSH5QqGcvRpsXVk= =cl5O -----END PGP SIGNATURE----- --nextPart5750140.2f8PWJG3B8-- From nobody Sun Jun 22 16:40:02 2025 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 4bQH5R0JPmz5ywVR; Sun, 22 Jun 2025 16:40:43 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (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 4bQH5P62MMz3lL0; Sun, 22 Jun 2025 16:40:41 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=Z+9d3MX+; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.60 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id B672E240563; Sun, 22 Jun 2025 18:40:39 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id DFD3B24028E; Sun, 22 Jun 2025 18:40:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1750610437; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=05i3VIbBEp2+2DaVuX2eTr6ekGK8CxvyTaF8RvdaIoA=; b=Z+9d3MX+X932bcKAPDz8hvm64uwtyzbGqlchlsAL8zWYUVcFKTXpjHWmAlai7dNuP/r2B4 RLcnn0rW6EF3TuggRsboJKfETgy8k1GD32HJ9dORU/JfBN6Twxp49URFtc16o2dpQRkZiC PMe1/4wj2QLziwNrHiJgl8SfQxvgh3LoEHPqZJjVWOdGSx2z7+ZrWTrPR9e6GVHvXs/l6w PgZwNwbbevFoLEoB/aioCpdIN1A4DFCiuCMfzUCMP2AIANz1Q3BTegPMob3Hl9SWV6Spnv AaVsmM9dNeV5NuaCcpQOGJLuh5zP+ZG+UC5/Hip6f7wf0YB6xLp4hQJ0N4WY6A== Received: from thor.sb211.local (dynamic-2a02-3100-195d-e402-e03d-4007-408b-047e.310.pool.telefonica.de [IPv6:2a02:3100:195d:e402:e03d:4007:408b:47e]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 883E9240283; Sun, 22 Jun 2025 18:40:37 +0200 (CEST) Date: Sun, 22 Jun 2025 18:40:02 +0200 From: A FreeBSD User To: FreeBSD CURRENT , FreeBSD Ports Subject: net/kea: [2.6.3_1]: Unable to open database: invalid path specified - only /var/db as folder allowed Message-ID: <20250622184029.76567686@thor.sb211.local> 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: multipart/signed; boundary="Sig_/_x/28Ea6BbPScpPaWTXICFS"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 5cebaf X-Rspamd-UID: b0b632 X-Spamd-Result: default: False [-4.67 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.995]; NEURAL_HAM_LONG(-0.58)[-0.575]; NEURAL_HAM_MEDIUM(-0.40)[-0.395]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.60:from]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-ports@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4bQH5P62MMz3lL0 X-Spamd-Bar: ---- --Sig_/_x/28Ea6BbPScpPaWTXICFS Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable After a recent update of net/kea (now at 2.6.3_1), kea rejects to startup b= ecause we have our lease database not within /var/db/kea, but in /pool/data/kea. According to the documentation provided at https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html#dhcpv4-server-confi= guration this is a intended behaviour since kea 2.7.9. For me, this change in 2.6.3 = came out of the blue and hit hard. To solve the problem for those having other folders in mind than the at com= pile time fixed one, one has to set the environment variable KEA_DHCP_DATA_DIR before start= up of kea. I have no clear idea were to put the proper definition of this environmenta= l variable BEFORE kea starts up. I tried using /etc/login.conf: [...] :setenv=3DBLOCKSIZE=3DK,KEA_DHCP_DATA_DIR=3D/pool/data/kea/:\ [...] but the downside is that the rc-script in /usr/local/etc/rc.d/kea requirs=20 REQUIRE: LOGIN ... before being effective. Consequence: net/kea doesn't start properly when KE= A_DHCP_DATA_DIR is set via /etc/login.conf. I guess the approach regarding /etc/login.conf is as wrong as changing the = rc.d script's milestone from NETWORK to LOGIN. Is there a clean way - apart from changing rc.d-script - to provide environ= ment variables at boottime? Thanks in advance, oh p.s. filed a PR: Bug 287598=20 --=20 A FreeBSD user --Sig_/_x/28Ea6BbPScpPaWTXICFS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaFgx/QAKCRCxzvs8Oqok r8bHAP4inPfORxl0kSkopKuP52i03M4VKWoAf4D1EHfJI/orcQD7ByBCxAibZIg2 GqMduN2iJXfCYqvS3cPbH2abrsbHnQc= =R5Bj -----END PGP SIGNATURE----- --Sig_/_x/28Ea6BbPScpPaWTXICFS--