Linux API

• Thread Index

• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH v4] signal: add taskfd_send_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v3] signal: add procfd_send_signal() syscall
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] Y2038: provide kernel support indication
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Y2038: provide kernel support indication
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH] Y2038: provide kernel support indication
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Y2038: provide kernel support indication
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH v3] signal: add procfd_send_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at nptl init and thread creation (v4)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH glibc 2/4] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: [PATCH v5 0/4] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v9 3/4] seccomp: add a return code to trap to userspace
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v9 3/4] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH 12/11] man-pages: copy_file_range updates
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v5 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v5 2/4] tools: sync uapi/linux/bpf.h
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v5 4/4] selftests: add a test for bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v5 1/4] bpf: respect size hint to BPF_PROG_TEST_RUN if present
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v5 0/4] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH 12/11] man-pages: copy_file_range updates
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] generic/43[014]: copy_range beyond source EOF should fail
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] generic/43[014]: copy_range beyond source EOF should fail
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v9 3/4] seccomp: add a return code to trap to userspace
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v9 2/4] seccomp: switch system call argument type to void *
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v9 1/4] seccomp: hoist struct seccomp_data recalculation higher
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [PATCH v9 1/4] seccomp: hoist struct seccomp_data recalculation higher
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v9 2/4] seccomp: switch system call argument type to void *
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v9 4/4] samples: add an example of seccomp user trap
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v9 3/4] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v9 0/4] seccomp trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v4 15/15] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v4 14/15] fanotify: add support for create/attrib/move/delete events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v4 08/15] fanotify: enable FAN_REPORT_FID init flag
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v4 07/15] fanotify: copy event fid info to user
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v4 00/15] fanotify: add support for more event types
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [apparmor] Security modules and sending signals within the same process
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v4 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: Security modules and sending signals within the same process
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Security modules and sending signals within the same process
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: Security modules and sending signals within the same process
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Security modules and sending signals within the same process
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• [PATCH v2 1/1] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Jürg Billeter <j@xxxxxxxxx>
• [PATCH v2 0/1] Add prctl to kill descendants on exit
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: Laurent Vivier <laurent@xxxxxxxxx>
• Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Joey Pabalinas <joeypabalinas@xxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Joey Pabalinas <joeypabalinas@xxxxxxxxx>
• Re: [PATCH] procfd_signal.2: document procfd_signal syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] procfd_signal.2: document procfd_signal syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH v4 4/4] selftests: add a test for bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v4 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v4 2/4] tools: sync uapi/linux/bpf.h
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v4 1/4] bpf: respect size hint to BPF_PROG_TEST_RUN if present
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v4 0/4] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• RE: Official Linux system wrapper library?
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• [PATCH v4 0/2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• [PATCH] prctl: add PR_{GET,SET}_KILL_DESCENDANTS_ON_EXIT
  • From: Jürg Billeter <j@xxxxxxxxx>
• [PATCH 0/1] Add prctl to kill descendants on exit
  • From: Jürg Billeter <j@xxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: William Kucharski <william.kucharski@xxxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: William Kucharski <william.kucharski@xxxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: Elvira Khabirova <lineprinter@xxxxxxxxxxxx>
• Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: Elvira Khabirova <lineprinter@xxxxxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: William Kucharski <william.kucharski@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Daniel Borkmann <daniel@xxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Szabolcs Nagy <Szabolcs.Nagy@xxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] Add /proc/pid_generation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH] Add /proc/pid_generation
  • From: Pavel Machek <pavel@xxxxxx>
• [PATCH v3 13/13] fanotify: report FAN_ONDIR to listener with FAN_REPORT_FID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 12/13] fanotify: add support for create/attrib/move/delete events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 08/13] fanotify: enable FAN_REPORT_FID init flag
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 04/13] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 00/13] fanotify: add support for more event types
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: Joey Pabalinas <joeypabalinas@xxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: Joey Pabalinas <joeypabalinas@xxxxxxxxx>
• [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO
  • From: Elvira Khabirova <lineprinter@xxxxxxxxxxxx>
• [PATCH RESEND v3 2/3] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Elvira Khabirova <lineprinter@xxxxxxxxxxxx>
• [PATCH RESEND v3 1/3] ptrace: pass type of a syscall-stop in ptrace_message
  • From: Elvira Khabirova <lineprinter@xxxxxxxxxxxx>
• [PATCH RESEND v3 0/3] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Elvira Khabirova <lineprinter@xxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: David Newall <glibc@xxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Daniel Borkmann <daniel@xxxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v4 2/4] namei: O_BENEATH-style path resolution flags
  • From: Aleksa Sarai <asarai@xxxxxxx>
• Re: [PATCH v4 2/4] namei: O_BENEATH-style path resolution flags
  • From: Aleksa Sarai <asarai@xxxxxxx>
• Re: [PATCH v4 2/4] namei: O_BENEATH-style path resolution flags
  • From: Aleksa Sarai <asarai@xxxxxxx>
• Re: [PATCH v4 2/4] namei: O_BENEATH-style path resolution flags
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Szabolcs Nagy <Szabolcs.Nagy@xxxxxxx>
• Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: David Newall <glibc@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v4 2/4] namei: O_BENEATH-style path resolution flags
  • From: Jürg Billeter <j@xxxxxxxxx>
• RE: [PATCH] Add /proc/pid_generation
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH -next 2/2] selftests/memfd: modify tests for F_SEAL_FUTURE_WRITE seal
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Szabolcs Nagy <Szabolcs.Nagy@xxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Rich Felker <dalias@xxxxxxxx>
• [PATCH v3 4/4] selftests: add a test for bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 3/4] libbpf: add bpf_prog_test_run_xattr
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 2/4] tools: sync uapi/linux/bpf.h
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 1/4] bpf: respect size hint to BPF_PROG_TEST_RUN if present
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 0/4] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [PATCH v2] UAPI: move RENAME_* definitions to separated file
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Add /proc/pid_generation
  • From: Kevin Easton <kevin@xxxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v2] signal: add procfd_signal() syscall
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Tim Murray <timmurray@xxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Add /proc/pid_generation
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [RFC PATCH v2] ptrace: add PTRACE_GET_SYSCALL_INFO request
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v2] Add /proc/pid_gen
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• [PATCH v2] Add /proc/pid_gen
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] Add /proc/pid_generation
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] Add /proc/pid_generation
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH] Add /proc/pid_generation
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH v4 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/5] cgroup: Introducing bypass mode
  • From: Michael Kerrisk <mtk.manpages@xxxxxxxxx>
• Re: [RFC PATCH v6 01/26] Documentation/x86: Add CET description
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jethro Beekman <jethro@xxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v6 01/26] Documentation/x86: Add CET description
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: [PATCH v2 0/4] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Y Song <ys114321@xxxxxxxxx>
• Re: [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size
  • From: Y Song <ys114321@xxxxxxxxx>
• [PATCH v2 4/4] selftests: add a test for bpf_prog_test_run output size
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v2 2/4] tools: sync uapi/linux/bpf.h
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v2 1/4] bpf: respect size hint to BPF_PROG_TEST_RUN if present
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v2 3/4] libbpf: require size hint in bpf_prog_test_run
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v2 0/4] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] procfd_signal.2: document procfd_signal syscall
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• [PATCH v2] procfd_signal.2: document procfd_signal syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Jan Kara <jack@xxxxxxx>
• [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc/<pid>/smaps
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [RFC PATCH 0/3] THP eligibility reporting via proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [PATCH v2 0/9] fanotify: add support for more event types
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v6 01/26] Documentation/x86: Add CET description
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• [PATCH -manpage 1/2] fcntl.2: Update manpage with new memfd F_SEAL_FUTURE_WRITE seal
  • From: "Joel Fernandes (Google)" <joel@xxxxxxxxxxxxxxxxx>
• [PATCH -manpage 2/2] memfd_create.2: Update manpage with new memfd F_SEAL_FUTURE_WRITE seal
  • From: "Joel Fernandes (Google)" <joel@xxxxxxxxxxxxxxxxx>
• [PATCH -next 2/2] selftests/memfd: modify tests for F_SEAL_FUTURE_WRITE seal
  • From: "Joel Fernandes (Google)" <joel@xxxxxxxxxxxxxxxxx>
• [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust
  • From: "Joel Fernandes (Google)" <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Daniel Borkmann <daniel@xxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v3 0/4] bpf: allow zero-initialising hash map seed
  • From: Daniel Borkmann <daniel@xxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v6 10/11] x86/vsyscall/64: Add ENDBR64 to vsyscall entry points
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• [RFC PATCH v6 03/26] x86/fpu/xstate: Change names to separate XSAVES system and user states
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 08/26] mm: Introduce VM_SHSTK for shadow stack memory
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 10/26] x86/mm: Change _PAGE_DIRTY to _PAGE_DIRTY_HW
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 13/26] x86/mm: Modify ptep_set_wrprotect and pmdp_set_wrprotect for _PAGE_DIRTY_SW
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 14/26] x86/mm: Shadow stack page fault error checking
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 11/26] x86/mm: Introduce _PAGE_DIRTY_SW
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 09/26] mm/mmap: Prevent Shadow Stack VMA merges
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 07/26] x86/cet/shstk: Add Kconfig option for user-mode shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 05/26] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 06/26] x86/cet: Add control protection exception handler
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 04/26] x86/fpu/xstate: Introduce XSAVES system states
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 02/26] x86/cpufeatures: Add CET CPU feature flags for Control-flow Enforcement Technology (CET)
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 01/26] Documentation/x86: Add CET description
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 16/26] mm: Handle THP/HugeTLB shadow stack page fault
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 15/26] mm: Handle shadow stack page fault
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 18/26] mm: Introduce do_mmap_locked()
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 17/26] mm: Update can_follow_write_pte/pmd for shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 23/26] x86/cet/shstk: Handle thread shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 21/26] x86/cet/shstk: Signal handling for shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 11/11] x86/cet: Add PTRACE interface for CET
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 10/11] x86/vsyscall/64: Add ENDBR64 to vsyscall entry points
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 07/11] x86/cet/ibt: Add ENDBR to op-code-map
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 06/11] x86/cet/ibt: Add arch_prctl functions for IBT
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 05/11] x86/cet/ibt: ELF header parsing for IBT
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 04/11] mm/mmap: Add IBT bitmap size to address space limit check
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 03/11] x86/cet/ibt: Add IBT legacy code bitmap setup function
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 02/11] x86/cet/ibt: User-mode indirect branch tracking support
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 00/11] Control-flow Enforcement: Branch Tracking, PTRACE
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 01/11] x86/cet/ibt: Add Kconfig option for user-mode Indirect Branch Tracking
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 26/26] x86/cet/shstk: Add Shadow Stack instructions to opcode map
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 25/26] x86/cet/shstk: Add arch_prctl functions for Shadow Stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 24/26] mm/mmap: Add Shadow stack pages to memory accounting
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 22/26] x86/cet/shstk: ELF header parsing of Shadow Stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 19/26] x86/cet/shstk: User-mode shadow stack support
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 20/26] x86/cet/shstk: Introduce WRUSS instruction
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 12/26] drm/i915/gvt: Update _PAGE_DIRTY to _PAGE_DIRTY_BITS
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• [RFC PATCH v6 00/26] Control-flow Enforcement: Shadow Stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v9 00/24] ILP32 for ARM64
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 1/2] proc: get process file descriptor from /proc/<pid>
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors (Larger pids)
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Dmitry Safonov <0x7f454c46@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Dave Martin <Dave.Martin@xxxxxxx>
• Re: [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v1 1/2] proc: get process file descriptor from /proc/<pid>
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• RE: [PATCH] proc: allow killing processes via file descriptors
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH v1 2/2] signal: add procfd_signal() syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• [PATCH] procfd_signal.2: document procfd_signal syscall
  • From: Christian Brauner <christian@xxxxxxxxxx>
• [PATCH v1 1/2] proc: get process file descriptor from /proc/<pid>
  • From: Christian Brauner <christian@xxxxxxxxxx>
• [PATCH v1 0/2] proc: allow signaling processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH v7 0/4] fanotify: introduce new event mask FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jethro Beekman <jethro@xxxxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] proc: allow killing processes via file descriptors
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 0/9] fanotify: add support for more event types
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH] proc: allow killing processes via file descriptors
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Y Song <ys114321@xxxxxxxxx>
• Re: [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size
  • From: Y Song <ys114321@xxxxxxxxx>
• Re: [PATCH 2/3] libbpf: require size hint in bpf_prog_test_run
  • From: Y Song <ys114321@xxxxxxxxx>
• Re: [PATCH 1/3] bpf: respect size hint to BPF_PROG_TEST_RUN if present
  • From: Y Song <ys114321@xxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Alan Cox <gnomes@xxxxxxxxxxxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: hpa@xxxxxxxxx
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: hpa@xxxxxxxxx
• Re: [PATCH v3 0/4] bpf: allow zero-initialising hash map seed
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v3 0/4] bpf: allow zero-initialising hash map seed
  • From: Song Liu <songliubraving@xxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Dave Martin <Dave.Martin@xxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH 1/3] bpf: respect size hint to BPF_PROG_TEST_RUN if present
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH 3/3] selftests: add a test for bpf_prog_test_run output size
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH 2/3] libbpf: require size hint in bpf_prog_test_run
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH 0/3] Fix unsafe BPF_PROG_TEST_RUN interface
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Dave Martin <Dave.Martin@xxxxxxx>
• [PATCH v3 1/4] bpf: allow zero-initializing hash map seed
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 2/4] bpf: move BPF_F_QUERY_EFFECTIVE after map flags
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 3/4] tools: sync linux/bpf.h
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 4/4] tools: add selftest for BPF_F_ZERO_SEED
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• [PATCH v3 0/4] bpf: allow zero-initialising hash map seed
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• [PATCH v2 9/9] fanotify: report FAN_ONDIR to listener for filename events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 8/9] fanotify: add support for create/attrib/move/delete events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 7/9] fanotify: support events with data type FSNOTIFY_EVENT_DENTRY
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 6/9] fanotify: enable FAN_REPORT_FID init flag
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 5/9] fanotify: copy event fid info to user
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 4/9] fanotify: encode file identifier for FAN_REPORT_FID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 3/9] fanotify: classify events that hold a file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 2/9] fanotify: define the structures to report a unique file identifier
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 1/9] fanotify: rename struct fanotify_{,perm_}event_info
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 0/9] fanotify: add support for more event types
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: hpa@xxxxxxxxx
• Re: extending wait4(2) or waitid(2) linux syscall
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Dave Martin <Dave.Martin@xxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH v5 06/27] x86/cet: Control protection exception handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 06/27] x86/cet: Control protection exception handler
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 06/27] x86/cet: Control protection exception handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v7 0/4] fanotify: introduce new event mask FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] fanotify: support limited functionality for unprivileged users
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] fanotify: support limited functionality for unprivileged users
  • From: Jan Kara <jack@xxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v7 1/4] fanotify: return only user requested event types in event mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Adam Borowski <kilobyte@xxxxxxxxxx>
• Re: [PATCH v7 0/4] fanotify: introduce new event mask FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Jan Kara <jack@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Szabolcs Nagy <Szabolcs.Nagy@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Dave Martin <Dave.Martin@xxxxxxx>
• Re: [PATCH v2] UAPI: move RENAME_* definitions to separated file
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• [PATCH v2] UAPI: move RENAME_* definitions to separated file
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v7 0/4] fanotify: introduce new event mask FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v7 1/4] fanotify: return only user requested event types in event mask
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v5 05/27] Documentation/x86: Add CET description
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Dave Martin <Dave.Martin@xxxxxxx>
• Re: [PATCH v5 05/27] Documentation/x86: Add CET description
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v7 0/4] fanotify: introduce new event mask FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v7 0/4] fanotify: introduce new event mask FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 1/4] fanotify: return only user requested event types in event mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v7 1/4] fanotify: return only user requested event types in event mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Jan Kara <jack@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH RESEND] UAPI: move RENAME_* definitions to separated file
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH RESEND] UAPI: move RENAME_* definitions to separated file
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Jan Kara <jack@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
• [PATCH v4 0/4] namei: O_* flags to restrict path resolution
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH v4 1/4] namei: split out nd->dfd handling to dirfd_path_init
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH v4 4/4] namei: aggressively check for nd->root escape on ".." resolution
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH v4 3/4] namei: O_THISROOT: chroot-like path resolution
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH v4 2/4] namei: O_BENEATH-style path resolution flags
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Szabolcs Nagy <Szabolcs.Nagy@xxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>