From nobody Sat Mar 15 11:26:54 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 4ZFJqk1XXyz5qcdm for ; Sat, 15 Mar 2025 11:27:30 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZFJqh0YNHz3vwy for ; Sat, 15 Mar 2025 11:27:28 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=D9alfuSK; dmarc=pass (policy=quarantine) header.from=leidinger.net; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1742038040; 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=ci1WVY/lSAb+5mZsR9xfwuskBdwMGiEABstlteTL0+4=; b=D9alfuSKn4WVatB5gomoTurl4DHdcffSKSw33jUQEoDQqAUUASf45nwKWrG+xQdRjjkUQ3 xgpLymm488NnUw59zMBfhpy/oTqP2KkN1/ee/t1b5iOUg2KkNsnj22JpS9iLgeLxAb+J1O 0jdHZYDRC1kf39sBOUxU472O3fQb5bHXV/oYG+i0dmJTAcuVrnS1k4qnV/owR9qNjfg4MW +vuBrifd8Gu51yYu9NuImnbd6OBh6abxb6gV83AH8HlyMqebqbU2cxnnPrAkWilUxmxu9b aVs+rEq8aGJ5oHVgyAG41gHk4DARbJLTbdJAPNiwABaABDKTGjiQ+dvekFCduQ== Date: Sat, 15 Mar 2025 12:26:54 +0100 From: Alexander Leidinger To: Current FreeBSD Subject: -fstack-clash-protection triggers something in setfstab() (was: Re: Strange file access issue in a recent -current (but not with the previous BE)) In-Reply-To: <5ebbe12dc6cb4e3fc00f0a07c03856e4@Leidinger.net> References: <5ebbe12dc6cb4e3fc00f0a07c03856e4@Leidinger.net> Message-ID: <2400b4d10d4804eef784768d050f6953@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_bea1f836c22f1b8fb7b1bfc7060d4c02"; micalg=pgp-sha256 X-Spamd-Result: default: False [-3.84 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_SPAM_LONG(0.99)[0.994]; NEURAL_HAM_SHORT(-0.99)[-0.993]; NEURAL_HAM_MEDIUM(-0.84)[-0.837]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; ONCE_RECEIVED(0.10)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; HAS_ORG_HEADER(0.00)[]; DKIM_TRACE(0.00)[leidinger.net:+]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; HAS_ATTACHMENT(0.00)[] X-Rspamd-Queue-Id: 4ZFJqh0YNHz3vwy X-Spamd-Bar: --- This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_bea1f836c22f1b8fb7b1bfc7060d4c02 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2025-02-26 16:20, schrieb Alexander Leidinger: > Hi, > > the working system is from 2025-01-25-141603, the non working system is > from 2025-02-21-115311. > > I'm not sure what the issue is exactly. I have traced down the change > of behavior to > ---snip--- > if not LIBC.setfstab(fstab_file_path.encode()): > ---snip--- > > In the working case LIBC.setfstab returns true (so with the not it > doesn't take this branch), and in the non-working case it returns false > (so with the not it takes this branch). > > Is someone aware of a change in this area? Searching for it > (https://cgit.freebsd.org/src/log/?qt=grep&q=setfstab) only brings the > initial commit. Interestingly my own commit triggers this issue. I bisected and commit 1c2ae9233b0ed4f6b92c59c0e4026f6ddc073e4a is causing this. This is the first ref which triggers the issue that iocage can not mount filesystems anymore. And the failing call in iocage seems to be the python LIBC.setfstab() call. And this only triggers, when the basesystem is compiled with the stack clash protection. I do not see any obvious issue in our setfstab code. Anyone with an idea? Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_bea1f836c22f1b8fb7b1bfc7060d4c02 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmfVZA4ACgkQEg2wmwP4 2IZ5vw/+JlvBO2JZii5MoFYAVLJSfiXnWnYPENEehJ8pfe4Fpt068M+PXFlf304s K7zYKsJ30PT2c0fogZPKcc35zDlZOZcFeRpMbzEghp9luAJCpVv09m/2C2blQiT5 RWJhowpWijFfrk3prsyD+ZlA1nTx8lmHLKukXRte/s7cbaBZMxd1gcAG7Sd0quYk 7Punq+OXj+P8fth2jUXcu/aeuRroNvitCgAZOYjA0t977f/yjzz5iEsOVIZpitlP GPaUG3qBhA8K41QvFGhcH0Qen/P1WXvdWnNT6Xq7SDwRtBiAo8X7I6LG++WR8MZg 6Q5qLRktDtVpH2bdvJkq2BbRqUg/TsbbCd5GfoZIj6cISUY/qKCn83Mirwf8ben7 lmnuQ9IbzwDwvFOtZ+kXoVgQ/xtwRB8fDoptomjZkePt6sitiguTeualJKsiwZg+ fuZt3SZLL0ngvqTUkqKvtfrsw9jEJaZF8wZ4MZI8dKwtzjyxqh4PE9bfm6Dg2GF2 EmK1DvDYgFxWUykYHs7Eq3v5xN6eVDGoOB2CWdgoXz7AyXaLDBQyicgWVYMWpnep UoqS1JvIzn/MMwQei0B2H9MOR7mxYtW96Nwg7Z/NGHCEvLzCA4DX4einfJbMu7VY 8FWNY2PkzLjNzE2cdTtBvisoq88KcRJq6m8wtRgOSakPTO8yq5M= =Kcuw -----END PGP SIGNATURE----- --=_bea1f836c22f1b8fb7b1bfc7060d4c02--