Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Aug 2025 23:27:05 +0200
From:      Alexander Leidinger <Alexander@Leidinger.net>
To:        Kyle Evans <kevans@freebsd.org>
Cc:        Xin LI <delphij@gmail.com>, Current <current@freebsd.org>
Subject:   Re: Big compat issue with a recent current (zfs + syscall)
Message-ID:  <c95294552f52dbf84451d32d80da1a63@Leidinger.net>
In-Reply-To: <ebe8f073-fc0b-4f8a-a0dc-01b9e90e971b@FreeBSD.org>
References:  <567997960c33b7a437a8a812b7d65379@Leidinger.net> <CAGMYy3smsx1Njq55Fqh0H4wBGEG8-TzzuhLJLA6JLdiy8Tu4UQ@mail.gmail.com> <ebe8f073-fc0b-4f8a-a0dc-01b9e90e971b@FreeBSD.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
Am 2025-08-21 23:14, schrieb Kyle Evans:
> On 8/21/25 11:16, Xin LI wrote:
>> On Thu, Aug 21, 2025 at 6:19 AM Alexander Leidinger 
>> <Alexander@leidinger.net <mailto:Alexander@leidinger.net>> wrote:
>> 
>>     Hi,
>> 
>>     I tried to update from -current as of 2025-08-11-154054 (CEST) to
>>     2025-08-20-075320. I've updated the kernel and base, but no jail.
>>     Result:
>> 
>>     1) Not all jails got up. For mysql I have the DB on a separate 
>> dataset,
>>     I attach the dataset to the jail (grep dataset /etc/rc.d/jail) to 
>> be
>>     able to manage it from within the jail. I got the message that the
>>     dataset is already attached (first start of the jail at boot). 
>> When I
>>     resolved this by simply not attaching the dataset, mysqld died 
>> with a
>>     bad syscall.
>> 
>>     2) A lot of processes inside jails segfaulted.
>> 
>>     I then updated the jails from the build. More processes came up, 
>> but
>>     some still died (e.g. php_fpm).
>> 
>>     At that point I reverted all back (this emails is handled via the 
>> jails
>>     on this host). I still have the BE which causes issues, in case 
>> someone
>>     needs to get some info out of it.
>> 
>>     I have not seen anything in UPDATING which suggests anything in 
>> this
>>     regard.
>> 
>>     src.conf:
>>     ---snip---
>>     WITHOUT_PROFILE=yes
>>     CFLAGS+=-DFTP_COMBINE_CWDS
>>     MALLOC_PRODUCTION=yes
>>     WITH_MALLOC_PRODUCTION=yes
>>     WITHOUT_LLVM_ASSERTIONS=yes
>>     KERNCONF=ANDROMEDA
>>     WITH_RETPOLINE=yes
>>     WITH_KERNEL_RETPOLINE=yes
>>     WITH_RELRO=yes
>>     WITH_BIND_NOW=yes
>>     OPT_INIT_ALL=zero
>>     WITH_ZEROREGS=yes
>>     WITHOUT_CLEAN=yes
>>     LOADER_GZIP_SUPPORT=no
>>     LOADER_BZIP2_SUPPORT=no
>>     LOADER_BIOS_TEXTONLY=no
>>     LOADER_NFS_SUPPORT=no
>>     LOADER_TFTP_SUPPORT=no
>>     LOADER_CD9660_SUPPORT=no
>>     ---snip---
>> 
>>     src-env.conf:
>>     ---snip---
>>     WITH_META_MODE=yes
>>     FORTIFY_SOURCE=2
>>     ---snip---
>> 
>>     Bye,
>>     Alexander.
>> 
>>     --     http://www.Leidinger.net <http://www.Leidinger.net>; 
>> Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
>>     http://www.FreeBSD.org <http://www.FreeBSD.org>    
>> netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF
>> 
>> Since you are using a custom kernel, is it possible that you didn't 
>> have COMPAT_FREEBSD14?  (Recently [gs]etgroups were changed, with 
>> compatibility syscalls moved to COMPAT_FREEBSD14).

UPDATING only mentions VMM stuff for COMPAT_FREEBSD14. I give this a try 
tomorrow. But would this also affect the zfs dataset stuff?

> I had wondered the same, but the use of 'segfault' gave me pause; these 
> would be SIGSYS rather than SIGSEGV, but that could just be a minor 
> terminology dispute.

Aug 20 10:35:32 Andromeda kernel: [566445] pid 52166 (auth), jid 50, uid 
143: exited on signal 6 (no core dump - sugid process denied by ke
rn.sugid_coredump)
Aug 20 10:35:37 Andromeda kernel: [566450] pid 52172 (auth), jid 50, uid 
143: exited on signal 6 (no core dump - sugid process denied by ke
rn.sugid_coredump)
Aug 20 10:35:44 Andromeda kernel: [566457] pid 52179 (auth), jid 50, uid 
143: exited on signal 6 (no core dump - sugid process denied by ke
rn.sugid_coredump)
Aug 20 10:35:51 Andromeda kernel: [566463] pid 52185 (auth), jid 50, uid 
143: exited on signal 6 (no core dump - sugid process denied by ke
rn.sugid_coredump)
Aug 20 10:35:56 Andromeda kernel: [566469] pid 52193 (auth), jid 50, uid 
143: exited on signal 6 (no core dump - sugid process denied by ke
rn.sugid_coredump)

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

iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAminjzkACgkQEg2wmwP4
2Ib/sQ//Sxcywi8Kbf/IAvXLDahNR/2JzxzEQMi4v0bFr+bhmJCeXwhWZ8RDfKjv
A9MwP8ibqgusrKEzbBh3ThQmkhwWDWwS/Yp1v+/MwRnQc18j7oOL59mtvwE3z8XN
KfrC2O+uQuD+VqAO3pT3k912hSl0tJz20NXfIMYIUISRA3i7TM07eG87zzy1w/y+
B26PBrSKgYM/MePN3/QVuhYUWAKh9eUqyNH30pA4EltxY3yjelECCJMpOkdeNPW5
Z5KeRh9tgpfBElatNhaOtBmbdUTFjllymJGE5gTLA1Hktmd6ZqQcmQT0ccHnuVFX
iDrJisgNqZPgHb42EAkYpqSThGHJXXJXfpLv09ZqdXmcM0vai+qMsHcxv3+OHI6z
OiReN9vOAwr86nH0edBpiaNHjcKajLd8STSIO0cMOWmnNAO1/6ouSuwv/r0Orzf2
/HLOUrT6X3hLkUk0KGTiW1sbvFtz4OCz8z0979XXzxKJYs/zml3PHIReFXkezsaM
GcB6tSSC0eXqPGTSTLsP5kVjQe0gpB2k/lqB2TRQ9jJXWycbUFZD6qZIvw6x77rZ
W3bVgHior2ndFxP+A4JjIIqIWDiameMUdqoPdWFEGLfKSmqcUGrTdqhXaVIHaFhE
kW480bMqHCkV/Z4xiaAOAqH9PHrMotO/Fz86h7VAIpLvrBw/xP8=
=XbR/
-----END PGP SIGNATURE-----
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c95294552f52dbf84451d32d80da1a63>