Linux API

• Thread Index

• 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>
• Re: Official Linux system wrapper library?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• [PATCH 3.16 330/366] fs/proc: Stop trying to report thread stacks
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Willy Tarreau <w@xxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Pavel Machek <pavel@xxxxxx>
• Re: Official Linux system wrapper library?
  • From: Willy Tarreau <w@xxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Willy Tarreau <w@xxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Willy Tarreau <w@xxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Willy Tarreau <w@xxxxxx>
• Re: Official Linux system wrapper library?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: Official Linux system wrapper library?
  • From: Willy Tarreau <w@xxxxxx>
• Official Linux system wrapper library?
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Michael Tirado <mtirado418@xxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v6] pidns: introduce syscall translate_pid
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH v5 04/27] x86/fpu/xstate: Add XSAVES system states for shadow stack
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pkeys: Reserve PKEY_DISABLE_READ
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• pkeys: Reserve PKEY_DISABLE_READ
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH v7 4/4] fanotify: introduce new event mask FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v7 3/4] fsnotify: refactor fsnotify_parent()/fsnotify() paired calls when event is on path
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v7 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v7 1/4] fanotify: return only user requested event types in event mask
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [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: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: [PATCH v5 02/15] sched/core: make sched_setattr able to tune the current policy
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v5 02/15] sched/core: make sched_setattr able to tune the current policy
  • From: Patrick Bellasi <patrick.bellasi@xxxxxxx>
• Re: [PATCH v5 02/15] sched/core: make sched_setattr able to tune the current policy
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v5 01/15] sched/core: uclamp: extend sched_setattr to support utilization clamping
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH v6 3/4] fanotify: introduce new event mask FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v6 2/4] fanotify: introduce new event mask FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v6 1/4] fanotify: return only user requested event types in event mask
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v6 0/4] fanotify: introduce new event masks FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jethro Beekman <jethro@xxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v2 1/3] bpf: allow zero-initializing hash map seed
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 21/27] x86/cet/shstk: Introduce WRUSS instruction
  • From: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v6 1/1] ns: add binfmt_misc to the user namespace
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v5 21/27] x86/cet/shstk: Introduce WRUSS instruction
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v5 21/27] x86/cet/shstk: Introduce WRUSS instruction
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: Upcoming fanotify API changes
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: Upcoming fanotify API changes
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Upcoming fanotify API changes
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH] fanotify: support limited functionality for unprivileged users
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH -next v2 0/3] sysvipc: introduce STAT_ANY commands
  • From: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: Supporting core-specific instruction sets (e.g. big.LITTLE) with restartable sequences
  • From: Andrew Pinski <pinskia@xxxxxxxxx>
• Re: Supporting core-specific instruction sets (e.g. big.LITTLE) with restartable sequences
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jethro Beekman <jethro@xxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jethro Beekman <jethro@xxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jethro Beekman <jethro@xxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx>
• Re: Supporting core-specific instruction sets (e.g. big.LITTLE) with restartable sequences
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: [RFC PATCH 1/2] glibc: Perform rseq(2) registration at nptl init and thread creation (v3)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH 1/2] glibc: Perform rseq(2) registration at nptl init and thread creation (v3)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Supporting core-specific instruction sets (e.g. big.LITTLE) with restartable sequences
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [RFC PATCH 2/2] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH 1/2] glibc: Perform rseq(2) registration at nptl init and thread creation (v3)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• RE: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: "y-goto@xxxxxxxxxxx" <y-goto@xxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram()
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram()
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 01/10] audit: collect audit task parameters
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram()
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram()
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: RFC: userspace exception fixups
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• RFC: userspace exception fixups
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH for 4.21 00/16] rseq updates, new cpu_opv system call (v2)
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: Laurent Vivier <laurent@xxxxxxxxx>
• Re: [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram()
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [RFC PATCH for 4.21 16/16] cpu-opv/selftests: Provide Makefile, scripts, gitignore
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 11/16] cpu-opv/selftests: Provide cpu-op library
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 10/16] arm: Wire up cpu_opv system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 09/16] powerpc: Wire up cpu_opv system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 15/16] cpu-opv/selftests: Provide parametrized tests
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 14/16] cpu-opv/selftests: Provide basic percpu ops test
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 13/16] cpu-opv/selftests: Provide percpu_op API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 12/16] cpu-opv/selftests: Provide basic test
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 06/16] cpu_opv: Provide cpu_opv system call (v9)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 07/16] cpu_opv: limit amount of virtual address space used by cpu_opv
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 08/16] x86: Wire up cpu_opv system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 05/16] mm: Provide is_vma_noncached
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 04/16] mm: Introduce vm_map_user_ram, vm_unmap_user_ram (v2)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram()
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 02/16] rseq/selftests: Adapt number of threads to the number of detected cpus
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 01/16] rseq/selftests: Expose reference counter to coexist with glibc (v2)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH for 4.21 00/16] rseq updates, new cpu_opv system call (v2)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH] Implement /proc/pid/kill
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v6 0/1] ns: introduce binfmt_misc namespace
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] Minimal non-child process exit notification support
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [RFC PATCH] Minimal non-child process exit notification support
  • From: Daniel Colascione <dancol@xxxxxxxxxx>
• Re: [RFC 00/20] ns: Introduce Time Namespace
  • From: Andrei Vagin <avagin@xxxxxxxxx>
• Re: [RFC PATCH] Implement /proc/pid/kill
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• RE: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: "y-goto@xxxxxxxxxxx" <y-goto@xxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH v6 1/1] ns: add binfmt_misc to the user namespace
  • From: Laurent Vivier <laurent@xxxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v8 2/2] samples: add an example of seccomp user trap
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [PATCH v8 2/2] samples: add an example of seccomp user trap
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• [PATCH v8 1/2] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v8 2/2] samples: add an example of seccomp user trap
  • From: Tycho Andersen <tycho@xxxxxxxx>
• [PATCH v8 0/2] seccomp trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH v3 0/2] sysctl: handle overflow for file-max
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [RFC 00/20] ns: Introduce Time Namespace
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [RFC 00/20] ns: Introduce Time Namespace
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [RFC 00/20] ns: Introduce Time Namespace
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v5 01/15] sched/core: uclamp: extend sched_setattr to support utilization clamping
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH v5 02/15] sched/core: make sched_setattr able to tune the current policy
  • From: Patrick Bellasi <patrick.bellasi@xxxxxxx>
• [PATCH v5 01/15] sched/core: uclamp: extend sched_setattr to support utilization clamping
  • From: Patrick Bellasi <patrick.bellasi@xxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v3 0/2] sysctl: handle overflow for file-max
  • From: Christian Brauner <christian@xxxxxxxxxx>
• [RFC PATCH] seccomp: Add protection keys into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v2 1/3] bpf: allow zero-initializing hash map seed
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [PATCH v2 2/3] tools: sync linux/bpf.h
  • From: Lorenz Bauer <lmb@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v6 1/1] ns: add binfmt_misc to the user namespace
  • From: Laurent Vivier <laurent@xxxxxxxxx>
• Re: [PATCH] seccomp: Add pkru into seccomp_data
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH] seccomp: Add pkru into seccomp_data
  • From: Michael Sammler <msammler@xxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [GIT PULL] siginfo updates for 4.20-rc1
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [RFC PATCH for 4.21 01/16] rseq/selftests: Add reference counter to coexist with glibc
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [GIT PULL] siginfo updates for 4.20-rc1
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
• Re: [PATCH v7 1/6] seccomp: add a return code to trap to userspace
  • From: Christian Brauner <christian@xxxxxxxxxx>
• Re: [PATCH 1/3] printk: Introduce per-console loglevel setting
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: [PATCH 01/34] vfs: syscall: Add open_tree(2) to reference or clone a mount [ver #12]
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH v7 1/6] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: [RFC 00/20] ns: Introduce Time Namespace
  • From: Andrei Vagin <avagin@xxxxxxxxx>
• Re: [RFC 00/20] ns: Introduce Time Namespace
  • From: Andrei Vagin <avagin@xxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2 6/5] statx: add STATX_RESULT_MASK flag
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v2 6/5] statx: add STATX_RESULT_MASK flag
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 09/10] audit: NETFILTER_PKT: record each container ID associated with a netNS
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 08/10] audit: add support for containerid to network namespaces
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 06/10] audit: add containerid support for tty_audit
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 05/10] audit: add support for non-syscall auxiliary records
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 04/10] audit: add containerid support for ptrace and signals
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 03/10] audit: log container info of syscalls
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 01/10] audit: collect audit task parameters
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] printk: Introduce per-console loglevel setting
  • From: Calvin Owens <calvinowens@xxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 02/10] audit: add container id
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 02/10] audit: add container id
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH ghak90 (was ghak32) V4 02/10] audit: add container id
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v2 6/5] statx: add STATX_RESULT_MASK flag
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH v2 2/5] uapi: deprecate STATX_ALL
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH v1 02/11] VFS permit cross device vfs_copy_file_range
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2 6/5] statx: add STATX_RESULT_MASK flag
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/5] uapi: deprecate STATX_ALL
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v2 2/5] uapi: deprecate STATX_ALL
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH v2 4/5] statx: don't clear STATX_ATIME on SB_RDONLY
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v2 3/5] statx: add STATX_ATTRIBUTES flag
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v2 2/5] uapi: deprecate STATX_ALL
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH v2 6/5] statx: add STATX_RESULT_MASK flag
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• Re: [PATCH v2 1/5] orangefs: fix request_mask misuse
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• [PATCH v2 4/5] statx: don't clear STATX_ATIME on SB_RDONLY
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• [PATCH v2 3/5] statx: add STATX_ATTRIBUTES flag
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• [PATCH v2 5/5] nfs: don't clear STATX_ATIME from result_mask
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• [PATCH v2 1/5] orangefs: fix request_mask misuse
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• [PATCH v2 2/5] uapi: deprecate STATX_ALL
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 3/3] statx: add STATX_ATTRIBUTES flag
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] printk: Introduce per-console loglevel setting
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: [PATCH v3 2/2] sysctl: handle overflow for file-max
  • From: Andrea Arcangeli <aarcange@xxxxxxxxxx>
• Re: [PATCH 1/3] orangefs: fix request_mask misuse
  • From: martin@xxxxxxxxxxxx
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 3/3] statx: add STATX_ATTRIBUTES flag
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• [PATCH 3/3] statx: add STATX_ATTRIBUTES flag
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• [PATCH 2/3] uapi: get rid of STATX_ALL
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• [PATCH 1/3] orangefs: fix request_mask misuse
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify: introduce new event type FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [PATCH v9 00/24] ILP32 for ARM64
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify: introduce new event type FAN_OPEN_EXEC_PERM
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Pavel Machek <pavel@xxxxxx>
• Re: statx(2) API and documentation
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Jan Kara <jack@xxxxxxx>
• Re: statx(2) API and documentation
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v7 1/6] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: statx(2) API and documentation
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: [PATCH v7 1/6] seccomp: add a return code to trap to userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v7 1/6] seccomp: add a return code to trap to userspace
  • From: Tycho Andersen <tycho@xxxxxxxx>
• Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: statx(2) API and documentation
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• statx(2) API and documentation
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [RFC PATCH for 4.21 06/16] cpu_opv: Provide cpu_opv system call (v8)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [RFC PATCH for 4.21 04/16] mm: Introduce vm_map_user_ram, vm_unmap_user_ram
  • From: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v3 0/3] namei: implement various lookup restriction AT_* flags
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [RFC PATCH for 4.21 06/16] cpu_opv: Provide cpu_opv system call (v8)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH for 4.21 03/16] sched: Implement push_task_to_cpu (v2)
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH for 4.21 04/16] mm: Introduce vm_map_user_ram, vm_unmap_user_ram
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH for 4.21 04/16] mm: Introduce vm_map_user_ram, vm_unmap_user_ram
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: Alan Jenkins <alan.christopher.jenkins@xxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 31/34] vfs: syscall: Add fspick() to select a superblock for reconfiguration [ver #12]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v4 3/3] fanotify: introduce new event type FAN_OPEN_EXEC_PERM
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v5 03/27] x86/fpu/xstate: Introduce XSAVES system states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v3 2/2] sysctl: handle overflow for file-max
  • From: Christian Brauner <christian@xxxxxxxxxx>
• [PATCH v5 3/3] fanotify: introduce new event type FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v5 2/3] fanotify: return only user requested event types in event mask
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v5 1/3] fanotify: introduce new event type FAN_OPEN_EXEC
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
  • From: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
• Re: [RFC PATCH for 4.21 06/16] cpu_opv: Provide cpu_opv system call (v8)
  • From: Srikar Dronamraju <srikar@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
  • From: Michal Hocko <mhocko@xxxxxxxxxx>