Linux API

• Thread Index

• Re: [PATCH v3 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 1/5] mm: pagewalk: add the ability to install PTEs
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4 2/4] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v4 2/4] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• [PATCH v3 5/5] selftests/mm: add self tests for guard page feature
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 4/5] tools: testing: update tools UAPI header for mman-common.h
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 1/5] mm: pagewalk: add the ability to install PTEs
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 0/5] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Marco Elver <elver@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v4 2/4] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v4 2/4] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• Re: [PATCH v4 1/4] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v2 5/5] selftests/mm: add self tests for guard page feature
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: (subset) [PATCH RFC v3 00/10] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 5/5] selftests/mm: add self tests for guard page feature
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: (subset) [PATCH RFC v3 00/10] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 1/5] mm: pagewalk: add the ability to install PTEs
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v2 1/5] mm: pagewalk: add the ability to install PTEs
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v4 2/4] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/5] implement lightweight guard pages
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• [PATCH v2 4/5] tools: testing: update tools UAPI header for mman-common.h
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 1/5] mm: pagewalk: add the ability to install PTEs
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 3/5] mm: madvise: implement lightweight guard page mechanism
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 5/5] selftests/mm: add self tests for guard page feature
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 0/5] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 2/5] mm: add PTE_MARKER_GUARD PTE marker
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v4 3/4] selftests: pidfd: add pidfd.h UAPI wrapper
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH 0/4] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 0/4] implement lightweight guard pages
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 0/4] implement lightweight guard pages
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v4 3/4] selftests: pidfd: add pidfd.h UAPI wrapper
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v4 3/4] selftests: pidfd: add pidfd.h UAPI wrapper
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH v4 3/4] selftests: pidfd: add pidfd.h UAPI wrapper
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4 3/4] selftests: pidfd: add pidfd.h UAPI wrapper
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• [PATCH v4 4/4] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v4 3/4] selftests: pidfd: add pidfd.h UAPI wrapper
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v4 1/4] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v4 2/4] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v4 0/4] introduce PIDFD_SELF* sentinels
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: The "make headers" requirement, revisited: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: The "make headers" requirement, revisited: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• The "make headers" requirement, revisited: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 2/3] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v3 0/3] introduce PIDFD_SELF* sentinels
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Suren Baghdasaryan <surenb@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: kernel test robot <oliver.sang@xxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Suren Baghdasaryan <surenb@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Suren Baghdasaryan <surenb@xxxxxxxxxx>
• Re: [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v20 2/6] security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits
  • From: sergeh@xxxxxxxxxx
• Re: [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: sergeh@xxxxxxxxxx
• Re: [PATCH v20 2/6] security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits
  • From: sergeh@xxxxxxxxxx
• Re: [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v20 2/6] security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v20 2/6] security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• [PATCH v20 6/6] samples/check-exec: Add an enlighten "inc" interpreter and 28 tests
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v20 3/6] selftests/exec: Add 32 tests for AT_CHECK and exec securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v20 5/6] samples/check-exec: Add set-exec
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v20 4/6] selftests/landlock: Add tests for execveat + AT_CHECK
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v20 2/6] security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v20 1/6] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v20 0/6] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [PATCH v2 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 2/3] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 0/3] introduce PIDFD_SELF* sentinels
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• [PATCH 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH 2/3] pidfd: add PIDFD_SELF* sentinels to refer to own thread/process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH 1/3] pidfd: extend pidfd_get_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH 0/3] introduce PIDFD_SELF* sentinels
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: (subset) [PATCH RFC v3 03/10] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH RFC v3 00/10] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: [PATCH RFC v3 03/10] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH RFC v3 10/10] selftests: mount_setattr: add CHECK_FIELDS selftest
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 09/10] mount_setattr: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 08/10] selftests: clone3: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 07/10] clone3: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 06/10] selftests: openat2: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 05/10] selftests: openat2: add 0xFF poisoned data after misaligned struct
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 04/10] openat2: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 03/10] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 02/10] sched_getattr: port to copy_struct_to_user
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 01/10] uaccess: add copy_struct_to_user helper
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 00/10] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [viro-vfs:work.xattr2] [fs/xattr] 64d47e878a: xfstests.xfs.046.fail
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [viro-vfs:work.xattr2] [fs/xattr] 64d47e878a: xfstests.xfs.046.fail
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [viro-vfs:work.xattr2] [fs/xattr] 64d47e878a: xfstests.xfs.046.fail
  • From: kernel test robot <oliver.sang@xxxxxxxxx>
• [PATCH RFT v11 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 3/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 2/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 1/8] arm64/gcs: Return a success value from gcs_alloc_thread_stack()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v11 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Yury Khrustalev <yury.khrustalev@xxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [RFC PATCH 3/3] selftests: pidfd: add tests for PIDFD_SELF
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [RFC PATCH 2/3] pidfd: add PIDFD_SELF sentinel to refer to own process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [RFC PATCH 1/3] pidfd: refactor pidfd_get_pid/to_pid() and de-duplicate pid lookup
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [RFC PATCH 0/3] introduce PIDFD_SELF
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH] dup.2: Add ENOMEM to ERRORS
  • From: Levi Zim via B4 Relay <devnull+rsworktech.outlook.com@xxxxxxxxxx>
• Re: [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• [PATCH v3] mm/madvise: unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 0/2] unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Pedro Falcato <pedro.falcato@xxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Pedro Falcato <pedro.falcato@xxxxxxxxx>
• [PATCH v2 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 2/2] selftests/mm: add test for process_madvise PR_MADV_SELF flag use
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v2 0/2] unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH] mm/madvise: retrieve mm before checking
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• [PATCH 1/2] mm/madvise: introduce PR_MADV_SELF flag to process_madvise()
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH 2/2] selftests/mm: add test for process_madvise PR_MADV_SELF flag use
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH 0/2] unrestrict process_madvise() for current process
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v11 1/8] Landlock: Add abstract UNIX socket restriction
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v11 1/8] Landlock: Add abstract UNIX socket restriction
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Christophe Leroy <christophe.leroy@xxxxxxxxxx>
• Re: [PATCH v23 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Miaohe Lin <linmiaohe@xxxxxxxxxx>
• [PATCH RFC v2 10/10] selftests: mount_setattr: add CHECK_FIELDS selftest
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 09/10] mount_setattr: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 08/10] selftests: clone3: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 07/10] clone3: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 06/10] selftests: openat2: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 05/10] selftests: openat2: add 0xFF poisoned data after misaligned struct
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 04/10] openat2: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 03/10] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 02/10] sched_getattr: port to copy_struct_to_user
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 01/10] uaccess: add copy_struct_to_user helper
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v2 00/10] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v4 2/2] generic/756: test name_to_handle_at(AT_HANDLE_MNT_ID_UNIQUE) explicitly
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v4 1/2] open_by_handle: verify u32 and u64 mount IDs
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v3 2/2] generic/756: test name_to_handle_at(AT_HANDLE_MNT_ID_UNIQUE) explicitly
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v3 2/2] generic/756: test name_to_handle_at(AT_HANDLE_MNT_ID_UNIQUE) explicitly
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v3 1/2] open_by_handle: verify u32 and u64 mount IDs
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH xfstests v3 2/2] generic/756: test name_to_handle_at(AT_HANDLE_MNT_ID_UNIQUE) explicitly
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v3 1/2] open_by_handle: verify u32 and u64 mount IDs
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH] Add provision to busyloop for events in ep_poll.
  • From: Joe Damato <jdamato@xxxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v2 1/2] statx: update headers to include newer statx fields
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v2 1/2] statx: update headers to include newer statx fields
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RFC 1/8] uaccess: add copy_struct_to_user helper
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RESEND v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH RESEND v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Jan Kara <jack@xxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [PATCH RESEND v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Jan Kara <jack@xxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH RFC 1/8] uaccess: add copy_struct_to_user helper
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• [PATCH RFC 8/8] selftests: clone3: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 7/8] selftests: openat2: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 6/8] selftests: openat2: add 0xFF poisoned data after misaligned struct
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 5/8] clone3: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 4/8] openat2: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 2/8] sched_getattr: port to copy_struct_to_user
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 1/8] uaccess: add copy_struct_to_user helper
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 0/8] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v1 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: "H.J. Lu" <hjl.tools@xxxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Szabolcs Nagy <nsz@xxxxxxxxxx>
• Re: [PATCH xfstests v1 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [PATCH RFC v2 0/4] mm: Introduce MAP_BELOW_HINT
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: [PATCH RFC v2 0/4] mm: Introduce MAP_BELOW_HINT
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH xfstests v1 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v1 1/2] statx: update headers to include newer statx fields
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RESEND v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RESEND v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RESEND v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: Recommended version handshake for FUSE clients
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Recommended version handshake for FUSE clients
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] random: vDSO getrandom() must reject invalid flag
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH] random: vDSO getrandom() must reject invalid flag
  • From: Yann Droneaud <yann@xxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Yangyu Chen <cyy@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Yangyu Chen <cyy@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Yangyu Chen <cyy@xxxxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• [PATCH RFT v10 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 3/8] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 2/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 1/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 2/8] selftests: Provide helper header for shadow stack testing
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Manpower Recruitment For Canada™
  • From: TFWP PROGRAM <admin@tandagat.online>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Willy Tarreau <w@xxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Willy Tarreau <w@xxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Levi Zim <rsworktech@xxxxxxxxxxx>
• [PATCH RFT v9 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 3/8] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 2/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 1/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Levi Zim <rsworktech@xxxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH v5 00/28] NT synchronization primitive driver
  • From: Elizabeth Figura <zfigura@xxxxxxxxxxxxxxx>
• Manpower Recruitment For Canada™
  • From: TFWP-PROGRAM <administrator@toneromala.space>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Kees Cook <kees@xxxxxxxxxx>
• [PATCH RFT v8 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 8/9] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 7/9] selftests/clone3: Explicitly handle child exits due to signals
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 6/9] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 5/9] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 2/9] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Pedro Falcato <pedro.falcato@xxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: "Nicholas Piggin" <npiggin@xxxxxxxxx>
• Re: [PATCH RFT v7 0/9] fork: Support shadow stacks in clone3()
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Pedro Falcato <pedro.falcato@xxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: kernel test robot <oliver.sang@xxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Rudi Heitbaum <rudi@xxxxxxxxxxxx>
• Re: [GIT PULL] asm-generic: fixes for 6.11
  • From: pr-tracker-bot@xxxxxxxxxx
• [GIT PULL] asm-generic: fixes for 6.11
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH RFC v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re:[PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH RFC v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH RFC v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Zijian Zhang <zijianzhang@xxxxxxxxxxxxx>
• Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Zijian Zhang <zijianzhang@xxxxxxxxxxxxx>
• Re: [PATCH RFC v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Josef Bacik <josef@xxxxxxxxxxxxxx>
• [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Arnd Bergmann <arnd@xxxxxxxxxx>
• Re: syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH RFC v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH v3] usb: gadget: f_fs: add capability for dfu run-time descriptor
  • From: Chris Wulff <crwulff@xxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• [PATCH v4] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 8/9] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 7/9] selftests/clone3: Explicitly handle child exits due to signals
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 6/9] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 5/9] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 2/9] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v3] usb: gadget: f_fs: add capability for dfu run-time descriptor
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re:[PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH 7/8] fs: add an ioctl to get the mnt ns id from nsfs
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH] nsfs: fix ioctl declaration
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: zijianzhang@xxxxxxxxxxxxx
• [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: zijianzhang@xxxxxxxxxxxxx
• [PATCH net-next v8 1/3] sock: support copying cmsgs to the user space in sendmsg
  • From: zijianzhang@xxxxxxxxxxxxx
• [PATCH net-next v8 0/3] net: A lightweight zero-copy notification mechanism for MSG_ZEROCOPY
  • From: zijianzhang@xxxxxxxxxxxxx
• Re: [PATCH 7/8] fs: add an ioctl to get the mnt ns id from nsfs
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH v2] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• Re: [PATCH] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v2] vfs: add RWF_NOAPPEND flag for pwritev2
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: "Jarkko Sakkinen" <jarkko@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: enh <enh@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Boris Lukashev <rageltman@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: mprotect PROT_SIGNAL
  • From: "Soni \"They/Them\" L." <fakedme@xxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: mprotect PROT_SIGNAL
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• [question] about NFS4 ACLs
  • From: Mathias Dufresne <mathias.dufresne@xxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH RFT v6 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Thiago Jung Bauermann <thiago.bauermann@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCH 0/2] uprobe: Fix uretprobe syscall wiring
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCH v23 4/4] selftests/vDSO: add tests for vgetrandom
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 3/4] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 2/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 0/4] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH] binfmt_elf: Fail execution of shared objects with ELIBEXEC (was: Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2))
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 5/5] samples/should-exec: Add set-should-exec
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• mprotect PROT_SIGNAL
  • From: "Soni \"They/Them\" L." <fakedme@xxxxxxxxx>
• [PATCH v22 4/4] selftests/vDSO: add tests for vgetrandom
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 3/4] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 2/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 0/4] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>