Public bug reported:
[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).
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Bionic)
Importance: Low
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
New
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).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925216/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
