Date: Sat, 20 Sep 2025 15:06:44 +0900 (JST) From: Yasuhiro Kimura <yasu@FreeBSD.org> To: kevans@FreeBSD.org Cc: freebsd-current@freebsd.org, olce@FreeBSD.org, kib@freebsd.org Subject: Re: Possible incompatible change with initgroups(3)? Message-ID: <20250920.150644.230386530666613770.yasu@FreeBSD.org> In-Reply-To: <332dadd2-5f70-4945-acc2-a7b1b874e66d@FreeBSD.org> References: <20250920.084312.1821713565920964352.yasu@FreeBSD.org> <20250920105317.41007477@darrin.worldsmith.org> <332dadd2-5f70-4945-acc2-a7b1b874e66d@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
From: Kyle Evans <kevans@FreeBSD.org> Subject: Re: Possible incompatible change with initgroups(3)? Date: Fri, 19 Sep 2025 22:45:35 -0500 > Yikes- the compat initgroups is broken by some botched symbol > resolution, and > I'm not really sure the ideal solution. The below patch functions as > a stop-gap, > but I'm not sure that it's ideal. > > The problem is that freebsd14_setgroups is only defined as a weak > alias for the > FBSD_1.0 version of setgroups in lib/libc/include/compat.h via > __sym_compat(). A > simple ktrace shows that it's ultimately getting resolved to accept(), > for whatever > reason, and thus we end up with the nonsensical error for anything > trying to take > the legacy initgroups() path. > > Thanks, > > Kyle Evans Thanks for patch. But as I wrote before the error messages have already disappeared by rebuilding and reinstalling Postfix package. So unfortunately I'm not able to test if your patch fixes the issue. --- Yasuhiro Kimurahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250920.150644.230386530666613770.yasu>