Skip to content

Fixes for the generic entry/exit framework

Ingo Molnar lkml 1 version Applied

Status from this message: The following commit has been merged into the core/entry branch of tip:

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 4 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2entry: Fix CONFIG_SECCOMP assumptionarch/Kconfig kernel/entry/common.c+6 -23 replies
2/2entry: Correct 'noinstr' attributeskernel/entry/common.c+2 -21 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] Fixes for the generic entry/exit framework

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(-)
Signature · 1 line
2.25.1