Re: ✘Bad system call
James Browning
jamesb192 at jamesb192.com
Mon Oct 27 00:18:36 UTC 2025
On 10/26/2025 4:49 PM PDT Gary E. Miller wrote:
>
>
> Yo James!
>
> On Sun, 26 Oct 2025 02:03:17 -0700 (PDT)
> James Browning via devel <devel at ntpsec.org> wrote:
>
> > clock_nanosleep from one of the threads on amd64.
> >
> > the helpful handler was not.
>
> Uh, lost me...
1. The problematic system call is a clock_nanosleep
2. It's getting called from a non-main thread (DNS?)
3. catchTrap was suppose to log something like the following
ERR: SIGSYS/seccomp bad syscall 115(clock_nanosleep)/0xC0000020
It stopped short of that
More information about the devel
mailing list