[PW_SID:1118352] arm64: entry: Convert to Generic Entry#2162
[PW_SID:1118352] arm64: entry: Convert to Generic Entry#2162linux-riscv-bot wants to merge 19 commits into
Conversation
The return value of __secure_computing() currently uses 0 to indicate that a system call should be allowed, and -1 to indicate that it should be blocked/killed. This 0/-1 pattern is non-intuitive for a security check function and makes the control flow at the call sites less readable. Furthermore, any potential future changes to these return values would require a high-risk, error-prone audit of all its users across different architectures. Sanitize this logic by converting the return type of __secure_computing() to a proper boolean, where 'true' explicitly means 'allow' and 'false' means 'fail/deny'. Update all the two dozen or so call sites across the tree to align with this new boolean semantic. No functional changes are intended, as the callers still return -1 to the lower-level assembly entry code upon seccomp denial. Suggested-by: Thomas Gleixner <tglx@kernel.org> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
…vdso_sigreturn() Currently, multiple architectures (LoongArch, RISC-V, S390, Powerpc) provide identical stubs for arch_syscall_is_vdso_sigreturn() that simply return false. This results in redundant boilerplate code across the tree. Introduce a default __weak implementation of arch_syscall_is_vdso_sigreturn() directly in syscall_user_dispatch.c that returns false. This allows architectures that do not utilize a vDSO sigreturn to entirely drop their redundant inline definitions. Architectures requiring a specialized check (such as x86) will continue to override this fallback with their strong symbol definitions. Clean up the redundant implementations in loongarch, riscv, s390 and powerpc. Cc: Thomas Gleixner <tglx@kernel.org> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Refactor syscall_trace_enter() and syscall_trace_exit() to move thread
flag reading to the caller. This aligns arm64's syscall trace enter/exit
function signature with generic entry framework.
[Changes]
1. Function signature changes:
- syscall_trace_enter(regs) → syscall_trace_enter(regs, flags)
- syscall_trace_exit(regs) → syscall_trace_exit(regs, flags)
2. Move flags reading to caller:
- Previously: read_thread_flags() called inside each function.
- Now: caller (like el0_svc_common) passes flags as parameter.
3. Update syscall.c:
- el0_svc_common() now passes flags to tracing functions and
re-fetches flags before entry/exit to handle potential TIF
updates.
[Why this matters]
- Aligns arm64 with the generic entry interface.
- Makes future migration to generic entry framework smoother.
No functional changes intended.
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Reviewed-by: Linus Walleij <linusw@kernel.org>
Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com>
Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com>
Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Use syscall_get_nr() to get syscall number for syscall_trace_enter().
This aligns arm64's internal tracing logic with the generic
entry framework.
[Changes]
1. Use syscall_get_nr() helper:
- Replace direct regs->syscallno access with
syscall_get_nr(current, regs).
- This helper is functionally equivalent to direct access on arm64.
2. Re-read syscall number after tracepoint:
- Re-fetch the syscall number after trace_sys_enter() as it may have
been modified by BPF or ftrace probes, matching generic entry behavior.
[Why this matters]
- Aligns arm64 with the generic entry interface.
- Makes future migration to generic entry framework smoother.
- Properly handles syscall number modifications by tracers.
- Uses standard architecture-independent helpers.
No functional changes intended.
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Reviewed-by: Linus Walleij <linusw@kernel.org>
Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com>
Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com>
Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Refactor syscall_trace_enter() by open-coding the seccomp check
to align with the generic entry framework.
[Background]
The generic entry implementation expands the seccomp check in-place
instead of using the secure_computing() wrapper. It directly tests
SYSCALL_WORK_SECCOMP and calls the underlying __secure_computing()
function to handle syscall filtering.
[Changes]
1. Open-code seccomp check:
- Instead of calling the secure_computing() wrapper, explicitly check
the 'flags' parameter for _TIF_SECCOMP.
- Call __secure_computing() directly if the flag is set.
[Why this matters]
- Aligns the arm64 syscall path with the generic entry implementation,
simplifying future migration to the generic entry framework.
- No functional changes are intended; seccomp behavior remains identical.
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Reviewed-by: Linus Walleij <linusw@kernel.org>
Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com>
Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com>
Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Extract syscall_enter_audit() helper and use syscall_get_arguments() to get syscall arguments, matching the generic entry implementation. The new code: - Checks audit_context() first to avoid unnecessary memcpy when audit is not active. - Uses syscall_get_arguments() helper instead of directly accessing regs fields. - Is now exactly equivalent to generic entry's syscall_enter_audit(). No functional changes. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Move the rseq_syscall() check earlier in the syscall exit path to ensure it operates on the original instruction pointer (regs->pc) before any potential modification by a tracer. [Background] When CONFIG_DEBUG_RSEQ is enabled, rseq_syscall() verifies that a system call was not executed within an rseq critical section by examining regs->pc. If a violation is detected, it triggers a SIGSEGV. [Problem] Currently, arm64 invokes rseq_syscall() after report_syscall_exit(). However, during report_syscall_exit(), a ptrace tracer can modify the task's instruction pointer via PTRACE_SETREGSET (with NT_PRSTATUS). This leads to an inconsistency where rseq may analyze a post-trace PC instead of the actual PC at the time of syscall exit. [Why this matters] The rseq check is intended to validate the execution context of the syscall itself. Analyzing a tracer-modified PC can lead to incorrect detection or missed violations. Moving the check earlier ensures rseq sees the authentic state of the task. [Alignment] This change aligns arm64 with: - Generic entry, which calls rseq_syscall() first. - arm32 implementation, which also performs the check before audit. [Impact] There is no functional change to signal delivery; SIGSEGV will still be processed in arm64_exit_to_user_mode() at the end of the exit path. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Thomas Gleixner <tglx@kernel.org> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
In preparation for moving arm64 over to the generic entry code, rename syscall_trace_exit() to syscall_exit_work(). The renamed function checks and prevents illegal system calls inside user-space rseq critical sections, while also handling tracing, auditing, and ptrace reporting. No functional changes. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Thomas Gleixner <tglx@kernel.org> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
In preparation for moving arm64 over to the generic entry code, restructure the fast-path syscall exit sequence within el0_svc_common(). Invert the nested conditional flags check so that when syscall work is pending or single-stepping is active, the corresponding exit work can be dispatched directly from within the fast-path bailout block. This clarifies the separation between the fast and slow exit paths, facilitating a cleaner transition to the generic entry state machine in subsequent patches. No functional changes. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
In preparation for moving arm64 over to the generic entry code, extract the core syscall exit tracing logic into a new inline helper, syscall_exit_to_user_mode_work(). This new helper encapsulates the thread flags retrieval and syscall exit processing, unifying the exit invocation paths across both the fast-path bailout block and the slow-path trace_exit fallback in el0_svc_common(). This restructuring significantly streamlines the architecture for the upcoming transition to the generic entry framework. No functional changes. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Streamline syscall_exit_to_user_mode_work() to align arm64's syscall exit behavior with the generic entry framework. [Rationale] 1. Unconditional RSEQ Execution: Relocate rseq_syscall() from the slow-path helper to the very beginning of syscall_exit_to_user_mode_work(). This ensures that RSEQ validation executes unconditionally across all exit scenarios, preventing it from being incorrectly bypassed on fast paths when CONFIG_DEBUG_RSEQ is active. 2. Centralized Exit Work Gating: Introduce the `_TIF_SYSCALL_EXIT_WORK` mask to aggregate exit thread flags and gate the execution of syscall_exit_work(). Gating audit_syscall_exit() behind this exit-time check introduces no functional changes. The `SYSCALL_AUDIT` flag and its context are statically allocated via audit_alloc() at fork time and only freed via audit_free() at do_exit(). Since the flag remains persistent and static throughout syscall execution, checking `_TIF_SYSCALL_AUDIT` in the mask is fully equivalent to evaluating audit_context() inside audit_syscall_exit(). [Changes] - Introduce the `_TIF_SYSCALL_EXIT_WORK` mask to bundle exit-specific flags. - Relocate rseq_syscall() to run unconditionally on the outermost layer. - Gate syscall_exit_work() via the new aggregated flag check to mirror the generic entry loop behavior. No functional changes intended. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Use exit-specific _TIF_SYSCALL_EXIT_WORK mask to filter out entry-only flags during the system call exit path checks. This aligns arm64 with the generic entry framework's SYSCALL_WORK_EXIT semantics. [Rationale] The current syscall exit path re-evaluates the thread flags using the global _TIF_SYSCALL_WORK mask. However, _TIF_SYSCALL_WORK includes flags that are strictly relevant to system call entry processing: 1. _TIF_SECCOMP: Seccomp filtering (__secure_computing()) only runs on entry. There is no seccomp callback for syscall exit. 2. _TIF_SYSCALL_EMU: In PTRACE_SYSEMU mode, the syscall is intercepted and skipped on entry. Since the syscall is never fully executed, reporting a separate syscall exit stop is unnecessary. [Changes] - _TIF_SYSCALL_EXIT_WORK: A new mask containing only flags requiring exit-time processing: _TIF_SYSCALL_TRACE, _TIF_SYSCALL_AUDIT, and _TIF_SYSCALL_TRACEPOINT. - Optimize re-evaluation check: Use _TIF_SYSCALL_EXIT_WORK inside the el0_svc_common() fast-path block to prevent redundant exit work execution when entry-only flags fluctuate or are synchronously modified under the hood. The outermost gating maintains _TIF_SYSCALL_WORK to preserve architectural entry-exit symmetry for tracers. - Cleanup: Remove the has_syscall_work() helper as it is no longer needed, supporting direct flag comparison to clearly distinguish between entry and exit mandates. [Impact] Unnecessary exit tracing and auditing processing are safely bypassed when entry-specific flags fluctuate during the fast-path re-check block. This safely streamlines the syscall exit sequence to mirror the generic entry loop behaviors without breaking debugger expectations. No functional changes intended Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Remove the redundant nested conditional check within the system call exit path of el0_svc_common() to streamline the exit sequence. When entering this fast-path block, CONFIG_DEBUG_RSEQ is guaranteed to be disabled. Under this constraint, the code logic inside the block becomes completely identical to the evaluation performed within syscall_exit_to_user_mode_work(). Therefore, invoking the inline helper directly achieves full logical equivalence while eliminating duplicate code nesting. No functional changes. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Remove the redundant conditional fast-path check within el0_svc_common() as both branches now execute the exact the same syscall_exit_to_user_mode_work(). Since both the conditional fast-path and the fallback slow-path now uniformly invoke syscall_exit_to_user_mode_work(), this explicit conditional branch is entirely redundant regardless of whether the evaluation is true or false. Removing it collapses the duplicated logic into a single, unconditional path. No functional changes. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Align the syscall exit reporting logic with the generic entry framework by skipping the exit stop when PTRACE_SYSEMU_SINGLESTEP is in effect. [Rationale] When a tracer uses PTRACE_SYSEMU_SINGLESTEP, both _TIF_SYSCALL_EMU and _TIF_SINGLESTEP flags are set. Currently, arm64 reports a syscall exit stop whenever _TIF_SINGLESTEP is set, regardless of the emulation state. However, as per the generic entry implementation (see include/linux/entry-common.h): "If SYSCALL_EMU is set, then the only reason to report is when SINGLESTEP is set (i.e. PTRACE_SYSEMU_SINGLESTEP). This syscall instruction has been already reported in syscall_trace_enter()." Since PTRACE_SYSEMU intercepts and skips the actual syscall execution, reporting a subsequent exit stop is redundant and inconsistent with the expected behavior of emulated system calls. [Changes] - Introduce report_single_step(): Add a helper to encapsulate the logic for deciding whether to report a single-step stop at syscall exit. It returns false if _TIF_SYSCALL_EMU is set, ensuring the emulated syscall does not trigger a duplicate report. - Update syscall_exit_work(): Use the new helper to determine the stepping state instead of directly checking _TIF_SINGLESTEP. [Impact] - PTRACE_SINGLESTEP: Continues to report exit stops for actual instructions. - PTRACE_SYSEMU: Continues to skip exit stops. - PTRACE_SYSEMU_SINGLESTEP: Now correctly skips the redundant exit stop, aligning arm64 with the generic entry infrastructure. Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Implement the generic entry framework for arm64 to handle system call entry and exit. This follows the migration of x86, RISC-V, and LoongArch, consolidating architecture-specific syscall tracing and auditing into the common kernel entry infrastructure, making it easier to enable advanced features on arm64, such as "Syscall User Dispatch" and "rseq time slice extension" optimization. [Background] Arm64 has already adopted generic IRQ entry. Completing the conversion to the generic syscall entry framework reduces architectural divergence, simplifies maintenance, and allows arm64 to automatically benefit from improvements in the common entry code. [Changes] 1. Kconfig and Infrastructure: - Select GENERIC_ENTRY and remove GENERIC_IRQ_ENTRY (now implied). - Migrate struct thread_info to use the syscall_work field instead of TIF flags for syscall-related tasks. 2. Thread Info and Flags: - Remove definitions for TIF_SYSCALL_TRACE, TIF_SYSCALL_AUDIT, TIF_SYSCALL_TRACEPOINT, TIF_SECCOMP, and TIF_SYSCALL_EMU. - Replace _TIF_SYSCALL_WORK and _TIF_SYSCALL_EXIT_WORK with the generic SYSCALL_WORK bitmask. - Map single-step state to SYSCALL_EXIT_TRAP in debug-monitors.c. 3. Architecture-Specific Hooks (asm/entry-common.h): - Implement arch_ptrace_report_syscall_entry() and _exit() by porting the existing arm64 logic to the generic interface. 4. Cleanup and Refactoring: - Remove redundant arm64-specific syscall tracing functions from ptrace.c, including syscall_trace_enter(), syscall_exit_work(), and related audit/step helpers. - Update el0_svc_common() in syscall.c to use the generic syscall_work checks and entry/exit call sites. [Why this matters] - Unified Interface: Aligns arm64 with the modern kernel entry standard. - Improved Maintainability: Bug fixes in kernel/entry/common.c now apply to arm64 automatically. - Feature Readiness: Simplifies the implementation of future cross-architecture syscall features. [Compatibility] This conversion maintains full ABI compatibility with existing userspace. The ptrace register-saving behavior, seccomp filtering, and syscall tracing semantics remain identical to the previous implementation. Additionally, since arm64 now does not select HAVE_GENERIC_TIF_BITS, there is no functional change regarding rseq management, as those generic entry pathways remain a no-op for this architecture." Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Thomas Gleixner <tglx@kernel.org> Cc: Peter Zijlstra <peterz@infradead.org> Tested-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com> Suggested-by: Kevin Brodsky <kevin.brodsky@arm.com> Suggested-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
After converting arm64 to Generic Entry framework, the compiler no longer inlines el0_svc_common() into its caller do_el0_svc(). This introduces a small but measurable overhead in the critical system call path. Manually forcing el0_svc_common() to be inlined restores the performance. Benchmarking with perf bench syscall basic on a Kunpeng 920 platform (based on v6.19-rc1) shows a ~1% performance uplift. Inlining this function reduces function prologue/epilogue overhead and allows for better compiler optimization in the hot system call dispatch path. | Metric | W/O this patch | With this patch | Change | | ---------- | -------------- | --------------- | --------- | | Total time | 2.195 [sec] | 2.171 [sec] | ↓1.1% | | usecs/op | 0.219575 | 0.217192 | ↓1.1% | | ops/sec | 4,554,260 | 4,604,225 | ↑1.1% | Cc: Mark Rutland <mark.rutland@arm.com> Cc: Will Deacon <will@kernel.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Reviewed-by: Ada Couprie Diaz <ada.coupriediaz@arm.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
Syscall User Dispatch (SUD) requires the signal trampoline code to not be intercepted. This is necessary to support returning with a locked selector while avoiding infinite recursion back into the signal handler. Implement arch_syscall_is_vdso_sigreturn() for arm64 to support this exclusion mechanism. For native 64-bit tasks, it checks whether the current PC matches the 'svc #0' instruction inside the vDSO sigreturn trampoline. SYM_CODE_START(__kernel_rt_sigreturn) mov x8, #__NR_rt_sigreturn svc #0 SYM_CODE_END(__kernel_rt_sigreturn) For COMPAT tasks, it verifies if the instruction falls within the architecture's 'sigpage' range, allowing the kernel to safely bypass dispatching syscalls originating from these areas back to userspace. Suggested-by: Kevin Brodsky <kevin.brodsky@arm.com> Suggested-by: kemal <kmal@cock.li> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 1: "[v16,01/18] seccomp: Convert __secure_computing() to return boolean" |
|
Patch 16: "[v16,16/18] arm64: entry: Convert to generic entry" |
|
Patch 16: "[v16,16/18] arm64: entry: Convert to generic entry" |
|
Patch 16: "[v16,16/18] arm64: entry: Convert to generic entry" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 17: "[v16,17/18] arm64: Inline el0_svc_common()" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
|
Patch 18: "[v16,18/18] arm64: vdso: Expose sigreturn address on vdso to the kernel" |
4d827ba to
89be0ce
Compare
2 participants
PR for series 1118352 applied to workflow__riscv__fixes
Name: arm64: entry: Convert to Generic Entry
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1118352
Version: 16