diff options
author | Evgeny Vereshchagin <evvers@ya.ru> | 2017-02-05 19:58:19 +0300 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2017-02-05 11:58:19 -0500 |
commit | 1b52793d5d597e62c8e35009baca165f1408687e (patch) | |
tree | e9bd414e5f920fcbaf77f3f21fe1d4ddbe3a9beb /rules | |
parent | 2604f8270cd106708070ebe448fcbed5a163f8c8 (diff) |
seccomp: don't ever try to add an ABI before removing the default native ABI (#5230)
https://github.com/systemd/systemd/issues/5215#issuecomment-277156262
libseccomp does not allow you to add architectures to a filter that
doesn't match the byte ordering of the architectures already added to
the filter (it would be a mess, not to mention largely pointless) and
since systemd attempts to add an ABI before removing the default native
ABI, you will always fail on Power (either due to ppc or ppc64le). The
fix is to remove the native ABI before adding a new ABI so you don't run
into problems with byte ordering.
You would likely see the same failure on a MIPS system.
Thanks @pcmoore!
Diffstat (limited to 'rules')
0 files changed, 0 insertions, 0 deletions