Date: Sat, 15 Mar 2025 12:26:54 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Current FreeBSD <freebsd-current@freebsd.org> Subject: -fstack-clash-protection triggers something in setfstab() (was: Re: Strange file access issue in a recent -current (but not with the previous BE)) Message-ID: <2400b4d10d4804eef784768d050f6953@Leidinger.net> In-Reply-To: <5ebbe12dc6cb4e3fc00f0a07c03856e4@Leidinger.net> References: <5ebbe12dc6cb4e3fc00f0a07c03856e4@Leidinger.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----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-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2400b4d10d4804eef784768d050f6953>