[Bug 1925216] Re: confusing but harmless warning messages printed about syscalls

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.48

---------------
systemd (237-3ubuntu10.48) bionic; urgency=medium

  * d/p/lp1925216-seccomp-rework-functions-for-parsing-system-call-fil.patch:
    Downgrade syscall group parsing failure logs to debug (LP: #1925216)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8c0181e24f7c0128a48c706d1f4b28ec0f225fd7
  * d/p/lp1929560-network-move-set-MAC-and-set-nomaster-operations-out.patch:
    Move link mac and master config out of link_up() (LP: #1929560)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d808ea22366ca7ba4b5bb32815ab0ca2eea8a49f
  * d/p/resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch,
    d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch,
    d/p/lp1880258-log-nxdomain-as-debug.patch,
    d/p/lp1785383-resolved-address-DVE-2018-0001.patch:
    - Use upstream patch for DVE-2018-0001 handling (LP: #1785383)
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b6258fda64c84c34b0f8026e6e29bcfffa8dc4f1

 -- Dan Streetman <ddstreet at canonical.com>  Thu, 27 May 2021 11:18:38
-0400

** Changed in: systemd (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

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

Title:
  confusing but harmless warning messages printed about syscalls

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [impact]

  systemd prints messages that complain about system calls such as:

  /lib/systemd/system/systemd-journald.service:33: Failed to parse
  system call, ignoring: pidfd_getfd

  [test case]

  boot bionic system with 4.15 kernel that does not support pidfd_getfd
  syscall

  [regression potential]

  any regression would prevent correct configuration of seccomp syscall
  filters, and/or failure to load/parse unit files that contain
  SystemCallFilter= directives

  [scope]

  this is needed only for b

  this is fixed upstream by commit
  13d92c6300edbb1369f97c2e1bef4c4096de8ddb which was included in v238,
  so this is fixed in focal and later

  this is not needed for x as seccomp handling is completely different
  in that older release

  [other info]

  as the warning states, the invalid system call is ignored, which is
  the correct action, and the patch to fix this just changes the log to
  debug instead of warning (along with consolidation of several flag
  params into a single flag enum). Thus, no actual change in behavior
  should occur (other than logging the messages as debug instead of
  warning).

  Also note that since this warning is the result of systemd's call into
  libseccomp2 to query the syscall, if libseccomp2 recognizes the
  syscall, the message will not be printed; the previous libseccomp2 for
  bionic (version 2.4.3) did not know the pidfd_getfd syscall, while the
  latest (version 2.5.1) does. So this is reproducable with libseccomp2
  version 2.4.3 but not the latest 2.5.1.

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