This fixes a !CONFIG_SECCOMP build bug found during CI testing,
plus adds a couple of 'noinstr' attribute ordering corrections
similar to 7f6fa101dfac and previous commits.
I resolved the CONFIG_SECCOMP problem by also making GENERIC_ENTRY
depend on HAVE_ARCH_SECCOMP_FILTER. This dependency was implicit
in the new code by virtue of x86 being a modern seccomp-filter
architecture.
The patch makes this explicit. I think it's reasonable to assume
any architecture that wants to make use of the generic code to
have modern seccomp framework. If they don't they'd have to
port it to the old secure_computing_strict() API anyway.
It's on top of the latest tip:x86/entry.
Thanks,
Ingo
Ingo Molnar (2):
entry: Fix CONFIG_SECCOMP assumption
entry: Correct 'noinstr' attributes
arch/Kconfig | 6 ++++--
kernel/entry/common.c | 6 ++++--
2 files changed, 8 insertions(+), 4 deletions(-)
--
2.25.1
