Starting it without going to the background confirmed my assumption:
../../chronyd -d -x -f /root/chrony-4.0/test/system/tmp/chronyd.conf -u root -F 
-1
2021-02-12T08:28:54Z chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC 
+PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2021-02-12T08:28:54Z Disabled control of system clock
2021-02-12T08:28:54Z Frequency 0.000 +/- 10000.000 ppm read from 
/root/chrony-4.0/test/system/tmp/driftfile
2021-02-12T08:28:54Z Loaded seccomp filter
Bad system call (core dumped)


with ltrace -rtS I can see this:

  0.004178 qsort(0xbfba10, 0, 144, 0x84808d)                                    
                                      = <void> <0.001344>
  0.001618 free(0xbf7750)                                                       
                                      = <void> <0.000946>
  0.001359 free(0xbea140)                                                       
                                      = <void> <0.001227>
  0.001634 __snprintf_chk(0xffc5c4e4, 4096, 1, 4096)                            
                                      = 38 <0.001835>
  0.002481 glob(0xffc5c4e4, 0, 0, 0xffc5c46c <unfinished ...>
  0.001822 SYS_322(-100, 0xffc5bf98, 0xa4800, 0)                                
                                      = 11 <0.001148>
  0.001684 SYS_397(11, 0xf75def08, 6144, 2047 <no return ...>
  0.759239 +++ killed by SIGSYS +++

That is statx?
https://github.com/torvalds/linux/blob/v5.10/arch/arm/tools/syscall.tbl#L414


You can test that with two builds of chrony 4.0 that we have in hirsute 
(-release/proposed).

$ltrace -rTS -- /usr/sbin/chronyd.old -d -x -f 
/root/chrony-4.0/test/system/tmp/chronyd.conf -u root -F 1
...
  0.000606 SYS_322(-100, 0xffcb3428, 0xa4800, 0)                                
                                      = 11 <0.001303>
  0.001932 SYS_397(11, 0xf7adcf08, 6144, 2047 <no return ...>
  0.738267 +++ killed by SIGSYS +++

$ltrace -rTS -- /usr/sbin/chronyd.new -d -x -f 
/root/chrony-4.0/test/system/tmp/chronyd.conf -u root -F 1
...
  0.000722 SYS_322(-100, 0xff99ed38, 0xa4800, 0)                                
                                      = 11 <0.000405>
  0.000555 SYS_397(11, 0xf79a2f08, 6144, 2047 <no return ...>
  0.763443 +++ killed by SIGSYS +++

If it is "SIGSYS" or "SIGSYS (Bad system call)" depends on our config, but 
isn't important.
We can see that the OLD and the NEW build both fail atm - so it is not anything 
that chrony introduced.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915006

Title:
  Consider merging 4.0-5 for Hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1915006/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to