linux-toradex.git/arch/um/kernel/skas/syscall.c, branch v6.7

x86/syscalls: Use __NR_syscalls instead of __NR_syscall_max

2021-05-20T13:03:59+00:00

__NR_syscall_max is only used by x86 and UML. In contrast, __NR_syscalls is
widely used by all the architectures.

Convert __NR_syscall_max to __NR_syscalls and adjust the usage sites.

This prepares x86 to switch to the generic syscallhdr.sh script.

Signed-off-by: Masahiro Yamada 
Signed-off-by: Thomas Gleixner 
Link: https://lore.kernel.org/r/20210517073815.97426-6-masahiroy@kernel.org

um: syscall.c: include

2020-04-29T19:22:04+00:00

Without CONFIG_SECCOMP, we don't get this include recursively
through the existing includes, thus failing the build on not
having __NR_syscall_max defined. Add the necessary include to
fix this.

Signed-off-by: Johannes Berg 
Acked-By: Anton Ivanov 
Signed-off-by: Richard Weinberger

um: Implement time-travel=ext

2020-03-29T21:29:08+00:00

This implements synchronized time-travel mode which - using a special
application on a unix socket - lets multiple machines take part in a
time-travelling simulation together.

The protocol for the unix domain socket is defined in the new file
include/uapi/linux/um_timetravel.h.

Signed-off-by: Johannes Berg 
Signed-off-by: Richard Weinberger

um: Move timer-internal.h to non-shared

2020-03-29T21:28:43+00:00

This file isn't really shared, it's only used on the kernel side,
not on the user side. Remove the include from the user-side and
move the file to a better place.

While at it, rename it to time-internal.h, it's not really just
timers but all kinds of things related to timekeeping.

Signed-off-by: Johannes Berg 
Signed-off-by: Richard Weinberger

seccomp: simplify secure_computing()

2019-10-10T21:55:24+00:00

Afaict, the struct seccomp_data argument to secure_computing() is unused
by all current callers. So let's remove it.
The argument was added in [1]. It was added because having the arch
supply the syscall arguments used to be faster than having it done by
secure_computing() (cf. Andy's comment in [2]). This is not true anymore
though.

/* References */
[1]: 2f275de5d1ed ("seccomp: Add a seccomp_data parameter secure_computing()")
[2]: https://lore.kernel.org/r/CALCETrU_fs_At-hTpr231kpaAd0z7xJN4ku-DvzhRU6cvcJA_w@mail.gmail.com

Signed-off-by: Christian Brauner 
Cc: Andy Lutomirski 
Cc: Thomas Gleixner 
Cc: Will Drewry 
Cc: Oleg Nesterov 
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-parisc@vger.kernel.org
Cc: linux-s390@vger.kernel.org
Cc: linux-um@lists.infradead.org
Cc: x86@kernel.org
Acked-by: Borislav Petkov 
Acked-by: Andy Lutomirski 
Link: https://lore.kernel.org/r/20190924064420.6353-1-christian.brauner@ubuntu.com
Signed-off-by: Kees Cook

um: Add SPDX headers to files in arch/um/kernel/

2019-09-15T19:37:17+00:00

Convert files to use SPDX header. All files are licensed under the
GPLv2.

Signed-off-by: Alex Dewar 
Signed-off-by: Richard Weinberger

um: Support time travel mode

2019-07-02T21:27:36+00:00

Sometimes it can be useful to run with "time travel" inside the
UML instance, for example for testing. For example, some tests
for the wireless subsystem and userspace are based on hwsim, a
virtual wireless adapter. Some tests can take a long time to
run because they e.g. wait for 120 seconds to elapse for some
regulatory checks. This obviously goes faster if it need not
actually wait that long, but time inside the test environment
just "bumps up" when there's nothing to do.

Add CONFIG_UML_TIME_TRAVEL_SUPPORT to enable code to support
such modes at runtime, selected on the command line:
 * just "time-travel", in which time inside the UML instance
   can move faster than real time, if there's nothing to do
 * "time-travel=inf-cpu" in which time also moves slower and
   any CPU processing takes no time at all, which allows to
   implement consistent behaviour regardless of host CPU load
   (or speed) or debug overhead.

An additional "time-travel-start=" parameter is also
supported in this case to start the wall clock at this time
(in unix epoch).

With this enabled, the test mentioned above goes from a runtime
of about 140 seconds (with startup overhead and all) to being
CPU bound and finishing in 15 seconds (on my slow laptop).

Signed-off-by: Johannes Berg 
Signed-off-by: Richard Weinberger

um/ptrace: Fix the syscall number update after a ptrace

2016-09-07T16:25:04+00:00

Update the syscall number after each PTRACE_SETREGS on ORIG_*AX.

This is needed to get the potentially altered syscall number in the
seccomp filters after RET_TRACE.

This fix four seccomp_bpf tests:
> [ RUN      ] TRACE_syscall.skip_after_RET_TRACE
> seccomp_bpf.c:1560:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(39) (26)
> seccomp_bpf.c:1561:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (22)
> [     FAIL ] TRACE_syscall.skip_after_RET_TRACE
> [ RUN      ] TRACE_syscall.kill_after_RET_TRACE
> TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 1)
> [     FAIL ] TRACE_syscall.kill_after_RET_TRACE
> [ RUN      ] TRACE_syscall.skip_after_ptrace
> seccomp_bpf.c:1622:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(39) (26)
> seccomp_bpf.c:1623:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (22)
> [     FAIL ] TRACE_syscall.skip_after_ptrace
> [ RUN      ] TRACE_syscall.kill_after_ptrace
> TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 1)
> [     FAIL ] TRACE_syscall.kill_after_ptrace

Fixes: 26703c636c1f ("um/ptrace: run seccomp after ptrace")

Signed-off-by: Mickaël Salaün 
Acked-by: Kees Cook 
Cc: Jeff Dike 
Cc: Richard Weinberger 
Cc: James Morris 
Cc: user-mode-linux-devel@lists.sourceforge.net
Signed-off-by: James Morris 
Signed-off-by: Kees Cook

um/ptrace: Fix the syscall_trace_leave call

2016-09-07T16:25:04+00:00

Keep the same semantic as before the commit 26703c636c1f: deallocate
audit context and fake a proper syscall exit.

This fix a kernel panic triggered by the seccomp_bpf test:
> [ RUN      ] global.ERRNO_valid
> BUG: failure at kernel/auditsc.c:1504/__audit_syscall_entry()!
> Kernel panic - not syncing: BUG!

Fixes: 26703c636c1f ("um/ptrace: run seccomp after ptrace")

Signed-off-by: Mickaël Salaün 
Acked-by: Kees Cook 
Cc: Jeff Dike 
Cc: Richard Weinberger 
Cc: James Morris 
Cc: user-mode-linux-devel@lists.sourceforge.net
Signed-off-by: James Morris 
Signed-off-by: Kees Cook

um/ptrace: run seccomp after ptrace

2016-06-14T17:54:47+00:00

Close the hole where ptrace can change a syscall out from under seccomp.

Signed-off-by: Kees Cook 
Cc: Jeff Dike 
Cc: Richard Weinberger 
Cc: user-mode-linux-devel@lists.sourceforge.net