Re: -fstack-clash-protection triggers something in setfstab()

Am 2025-03-15 14:33, schrieb Kyle Evans: [+grembo@ for iocage] On 3/15/25 06:26, Alexander Leidinger wrote: 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 e

-fstack-clash-protection triggers something in setfstab() (was: Re: Strange file access issue in a recent -current (but not with the previous BE))

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()

Re: -fstack-clash-protection triggers something in setfstab()

[+grembo@ for iocage] On 3/15/25 06:26, Alexander Leidinger wrote: 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