Date: Thu, 21 Aug 2025 16:29:08 -0700 From: Xin LI <delphij@gmail.com> To: Kyle Evans <kevans@freebsd.org> Cc: Alexander Leidinger <Alexander@leidinger.net>, Current <current@freebsd.org> Subject: Re: Big compat issue with a recent current (zfs + syscall) Message-ID: <CAGMYy3tNc7B--219rM8cFT7F1qw5WXD8J9%2BZVS40CC-Cj9GVjA@mail.gmail.com> In-Reply-To: <a427641d-3fda-4155-9ada-ba430c2231d6@FreeBSD.org> References: <567997960c33b7a437a8a812b7d65379@Leidinger.net> <CAGMYy3smsx1Njq55Fqh0H4wBGEG8-TzzuhLJLA6JLdiy8Tu4UQ@mail.gmail.com> <ebe8f073-fc0b-4f8a-a0dc-01b9e90e971b@FreeBSD.org> <c95294552f52dbf84451d32d80da1a63@Leidinger.net> <a427641d-3fda-4155-9ada-ba430c2231d6@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Thu, Aug 21, 2025 at 2:56 PM Kyle Evans <kevans@freebsd.org> wrote: [...] > I don't think I'd expect it to help with zfs dataset stuff. > There are also some recent ZFS changes, but I don't know (didn't have read through all changes) if there are something related. > >> 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) > > > > SIGABRT would seem to imply something like an assertion being tripped, > which is a bit unusual. Might need to flip > kern.sugid_coredump for a minute and see if you can gather some more > context from a coredump. > Well, yes (it's somewhat unusual) and no (I think it's expected behavior here): It's not unusual for a program to explicitly abort() when a setgroups() call failed, though: if I was the programmer who wanted to drop privileges and failed, showing some error message and abort() as soon as possible would be a reasonable choice (IMHO) because I wouldn't have a lot of other remedies, so to me it sounded reasonable here, especially when Alexander saw some missing system calls earlier. Cheers, [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Aug 21, 2025 at 2:56 PM Kyle Evans <<a href="mailto:kevans@freebsd.org">kevans@freebsd.org</a>> wrote:</div><div dir="ltr" class="gmail_attr"><span style="font-family:monospace,monospace">[...]</span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> I don't think I'd expect it to help with zfs dataset stuff.<br></blockquote><div><br></div><div><span class="gmail_default" style="font-family:monospace,monospace">There are also some recent ZFS changes, but I don't know (didn't have read through all changes) if there are something related.</span><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> >> 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.<br> > <br> > 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<br> > rn.sugid_coredump)<br> > 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<br> > rn.sugid_coredump)<br> > 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<br> > rn.sugid_coredump)<br> > 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<br> > rn.sugid_coredump)<br> > 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<br> > rn.sugid_coredump)<br> > <br> <br> SIGABRT would seem to imply something like an assertion being tripped, which is a bit unusual. Might need to flip<br> kern.sugid_coredump for a minute and see if you can gather some more context from a coredump.<br></blockquote><div><br></div><div class="gmail_default" style="font-family:monospace,monospace">Well, yes (it's somewhat unusual) and no (I think it's expected behavior here): It's not unusual for a program to explicitly abort() when a setgroups() call failed, though: if I was the programmer who wanted to drop privileges and failed, showing some error message and abort() as soon as possible would be a reasonable choice (IMHO) because I wouldn't have a lot of other remedies, so to me it sounded reasonable here, especially when Alexander saw some missing system calls earlier.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Cheers,</div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGMYy3tNc7B--219rM8cFT7F1qw5WXD8J9%2BZVS40CC-Cj9GVjA>