Linux API

• Thread Index

• [PATCH v7 27/41] x86/mm: Warn if create Write=0,Dirty=1 with raw prot
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 26/41] mm: Warn on shadow stack memory in wrong vma
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 25/41] x86/mm: Introduce MAP_ABOVE4G
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 10/41] x86/mm: Move pmd_write(), pud_write() up in the file
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 21/41] mm: Add guard pages around a shadow stack.
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 07/41] x86: Move control protection handler to separate file
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 20/41] x86/mm: Teach pte_mkwrite() about stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 11/41] mm: Introduce pte_mkwrite_kernel()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 19/41] x86/mm: Check shadow stack page fault errors
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 16/41] x86/mm: Start actually marking _PAGE_SAVED_DIRTY
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 24/41] mm: Don't allow write GUPs to shadow stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 06/41] x86/fpu: Add helper for modifying xstate
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 13/41] mm: Make pte_mkwrite() take a VMA
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 23/41] mm: Re-introduce vm_flags to do_mmap()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 22/41] mm/mmap: Add shadow stack pages to memory accounting
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 15/41] x86/mm: Update ptep/pmdp_set_wrprotect() for _PAGE_SAVED_DIRTY
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 18/41] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 17/41] mm: Move VM_UFFD_MINOR_BIT from 37 to 38
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 09/41] x86/mm: Remove _PAGE_DIRTY from kernel RO pages
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 08/41] x86/shstk: Add user control-protection fault handler
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 12/41] s390/mm: Introduce pmd_mkwrite_kernel()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 04/41] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 03/41] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 05/41] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 02/41] x86/shstk: Add Kconfig option for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 01/41] Documentation/x86: Add CET shadow stack description
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v7 00/41] Shadow stacks for userspace
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v2] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v6 02/11] LSM: Maintain a table of LSM attribute data
  • From: kernel test robot <oliver.sang@xxxxxxxxx>
• Re: [PATCH v2] rseq.2: New man page for the rseq(2) API
  • From: Alex Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 28/41] x86: Introduce userspace API for shadow stack
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v6 28/41] x86: Introduce userspace API for shadow stack
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted
  • From: kirill.shutemov@xxxxxxxxxxxxxxx
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall
  • From: Deepak Gupta <debug@xxxxxxxxxxxx>
• Re: [PATCH v6 12/41] s390/mm: Introduce pmd_mkwrite_kernel()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v6 19/41] x86/mm: Check shadow stack page fault errors
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 04/11] LSM: syscalls for current process attributes
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v6 12/41] s390/mm: Introduce pmd_mkwrite_kernel()
  • From: Heiko Carstens <hca@xxxxxxxxxxxxx>
• Re: [PATCH v6 06/11] LSM: wireup Linux Security Module syscalls
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH v6 04/11] LSM: syscalls for current process attributes
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v6 04/11] LSM: syscalls for current process attributes
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [RFC PATCH 0/2] Add flag as THP allocation hint for memfd_restricted() syscall
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall
  • From: Deepak Gupta <debug@xxxxxxxxxxxx>
• Re: [PATCH v6 19/41] x86/mm: Check shadow stack page fault errors
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 18/41] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: Deepak Gupta <debug@xxxxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• [PATCH v6 09/11] AppArmor: Add selfattr hooks
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 11/11] LSM: selftests for Linux Security Module syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 10/11] SELinux: Add selfattr hooks
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 07/11] LSM: Helpers for attribute names and filling an lsm_ctx
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 08/11] Smack: implement setselfattr and getselfattr hooks
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 06/11] LSM: wireup Linux Security Module syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 03/11] proc: Use lsmids instead of lsm names for attrs
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 04/11] LSM: syscalls for current process attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 05/11] LSM: Create lsm_module_list system call
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 02/11] LSM: Maintain a table of LSM attribute data
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 00/11] LSM: Three basic syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v6 01/11] LSM: Identify modules by more than name
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Alexey Kardashevskiy <aik@xxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 22/41] mm/mmap: Add shadow stack pages to memory accounting
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 24/41] mm: Don't allow write GUPs to shadow stack memory
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 24/41] mm: Don't allow write GUPs to shadow stack memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 18/41] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 22/41] mm/mmap: Add shadow stack pages to memory accounting
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: Pengfei Xu <pengfei.xu@xxxxxxxxx>
• Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 20/41] x86/mm: Teach pte_mkwrite() about stack memory
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 22/41] mm/mmap: Add shadow stack pages to memory accounting
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 25/41] x86/mm: Introduce MAP_ABOVE4G
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 27/41] x86/mm: Warn if create Write=0,Dirty=1 with raw prot
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 18/41] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: John Allen <john.allen@xxxxxxx>
• Re: [PATCH v6 22/41] mm/mmap: Add shadow stack pages to memory accounting
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 19/41] x86/mm: Check shadow stack page fault errors
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 18/41] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 12/41] s390/mm: Introduce pmd_mkwrite_kernel()
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 11/41] mm: Introduce pte_mkwrite_kernel()
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 11/41] mm: Introduce pte_mkwrite_kernel()
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v6 00/41] Shadow stacks for userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [RFC PATCH 0/2] Add flag as THP allocation hint for memfd_restricted() syscall
  • From: Yuan Yao <yuan.yao@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [PATCH v6 38/41] x86/fpu: Add helper for initing features
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 27/41] x86/mm: Warn if create Write=0,Dirty=1 with raw prot
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 25/41] x86/mm: Introduce MAP_ABOVE4G
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 20/41] x86/mm: Teach pte_mkwrite() about stack memory
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 12/41] s390/mm: Introduce pmd_mkwrite_kernel()
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 11/41] mm: Introduce pte_mkwrite_kernel()
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v10 2/3] cachestat: implement cachestat syscall
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v10 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v10 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v10 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v10 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v10 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• [PATCH v10 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v10 3/3] selftests: Add selftests for cachestat
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v10 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v10 0/3] cachestat: a new syscall for page cache state of files
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v6 41/41] x86/shstk: Add ARCH_SHSTK_STATUS
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 39/41] x86: Add PTRACE interface for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 40/41] x86/shstk: Add ARCH_SHSTK_UNLOCK
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 37/41] selftests/x86: Add shadow stack test
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 38/41] x86/fpu: Add helper for initing features
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 36/41] x86/shstk: Wire in shadow stack interface
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 35/41] x86: Expose thread features in /proc/$PID/status
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 34/41] x86/shstk: Support WRSS for userspace
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 32/41] x86/shstk: Handle signals for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 30/41] x86/shstk: Handle thread shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 31/41] x86/shstk: Introduce routines modifying shstk
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 28/41] x86: Introduce userspace API for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 27/41] x86/mm: Warn if create Write=0,Dirty=1 with raw prot
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 26/41] mm: Warn on shadow stack memory in wrong vma
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 25/41] x86/mm: Introduce MAP_ABOVE4G
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 24/41] mm: Don't allow write GUPs to shadow stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 22/41] mm/mmap: Add shadow stack pages to memory accounting
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 23/41] mm: Re-introduce vm_flags to do_mmap()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 21/41] mm: Add guard pages around a shadow stack.
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 18/41] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 20/41] x86/mm: Teach pte_mkwrite() about stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 19/41] x86/mm: Check shadow stack page fault errors
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 17/41] mm: Move VM_UFFD_MINOR_BIT from 37 to 38
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 16/41] x86/mm: Start actually marking _PAGE_SAVED_DIRTY
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 15/41] x86/mm: Update ptep/pmdp_set_wrprotect() for _PAGE_SAVED_DIRTY
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 14/41] x86/mm: Introduce _PAGE_SAVED_DIRTY
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 11/41] mm: Introduce pte_mkwrite_kernel()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 12/41] s390/mm: Introduce pmd_mkwrite_kernel()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 10/41] x86/mm: Move pmd_write(), pud_write() up in the file
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 07/41] x86: Move control protection handler to separate file
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 09/41] x86/mm: Remove _PAGE_DIRTY from kernel RO pages
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 08/41] x86/shstk: Add user control-protection fault handler
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 06/41] x86/fpu: Add helper for modifying xstate
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 05/41] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 04/41] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 03/41] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 02/41] x86/shstk: Add Kconfig option for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 01/41] Documentation/x86: Add CET shadow stack description
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v6 00/41] Shadow stacks for userspace
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [RFC PATCH 2/2] selftests: restrictedmem: Add selftest for RMFD_HUGEPAGE
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• [RFC PATCH 1/2] mm: restrictedmem: Add flag as THP allocation hint for memfd_restricted() syscall
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• [RFC PATCH 0/2] Add flag as THP allocation hint for memfd_restricted() syscall
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• [RFC PATCH 2/2] selftests: restrictedmem: Check hugepage-ness of shmem file backing restrictedmem fd
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• [RFC PATCH 0/2] Providing mount for memfd_restricted() syscall
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• [PATCH v2] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: Deepak Gupta <debug@xxxxxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
• Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• [PATCH 1/1] rseq.2: New man page for the rseq(2) API
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: Deepak Gupta <debug@xxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: Deepak Gupta <debug@xxxxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: copy on write for splice() from file to pipe?
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jeremy Allison <jra@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jeremy Allison <jra@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 03/14] Move COMPAT_ATM_ADDPARTY to net/atm/svc.c
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH 03/14] Move COMPAT_ATM_ADDPARTY to net/atm/svc.c
  • From: Thomas Huth <thuth@xxxxxxxxxx>
• Re: [PATCH 06/14] Move ep_take_care_of_epollwakeup() to fs/eventpoll.c
  • From: Thomas Huth <thuth@xxxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Jeremy Allison <jra@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] riscv: Bump COMMAND_LINE_SIZE value to 1024
  • From: Alex Ghiti <alex@xxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: copy on write for splice() from file to pipe?
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Borislav Petkov <bp@xxxxxxxxx>
• copy on write for splice() from file to pipe?
  • From: Stefan Metzmacher <metze@xxxxxxxxx>
• Re: [PATCH] riscv: Bump COMMAND_LINE_SIZE value to 1024
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations
  • From: David Vernet <void@xxxxxxxxxxxxx>
• Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations
  • From: Toke Høiland-Jørgensen <toke@xxxxxxxxxx>
• Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations
  • From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
• Re: [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• [PATCH v7 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v7 2/3] fanotify: define struct members to hold response decision context
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v7 1/3] fanotify: Ensure consistent variable type for response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• [PATCH v9 3/3] selftests: Add selftests for cachestat
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v9 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v9 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v9 0/3] cachestat: a new syscall for page cache state of files
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations
  • From: patchwork-bot+netdevbpf@xxxxxxxxxx
• Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations
  • From: David Vernet <void@xxxxxxxxxxxxx>
• [PATCH bpf-next v3 0/1] Document kfunc lifecycle / stability expectations
  • From: David Vernet <void@xxxxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: "Serge Hallyn (shallyn)" <shallyn@xxxxxxxxx>
• Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4] fcntl: Add 32bit filesystem mode
  • From: Conlan Cesar <conlanc@xxxxxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• RE: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Wang, Wei W" <wei.w.wang@xxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Ackerley Tng <ackerleytng@xxxxxxxxxx>
• Re: [PATCH v8 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 7/9] KVM: Update lpage info when private/shared memory are mixed
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v8 2/3] cachestat: implement cachestat syscall
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v8 2/3] cachestat: implement cachestat syscall
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v8 2/3] cachestat: implement cachestat syscall
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v8 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v8 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v8 3/3] selftests: Add selftests for cachestat
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v8 0/3] cachestat: a new syscall for page cache state of files
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v7 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v7 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v5 00/39] Shadow stacks for userspace
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• RE: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: "Schimpe, Christina" <christina.schimpe@xxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Liam Merwick <liam.merwick@xxxxxxxxxx>
• RE: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: "Schimpe, Christina" <christina.schimpe@xxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: Kees Cook <kees@xxxxxxxxxx>
• [PATCH v7 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v7 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Liam Merwick <liam.merwick@xxxxxxxxxx>
• Re: [PATCH v7 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v7 2/3] cachestat: implement cachestat syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• [PATCH v7 3/3] selftests: Add selftests for cachestat
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v7 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v7 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v7 0/3] cachestat: a new syscall for page cache state of files
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Huang, Kai" <kai.huang@xxxxxxxxx>
• Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v5 00/39] Shadow stacks for userspace
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Jarkko Sakkinen <jarkko@xxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Jarkko Sakkinen <jarkko@xxxxxxxxxx>
• Re: [PATCH v5 00/39] Shadow stacks for userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v6 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v5 00/39] Shadow stacks for userspace
  • From: John Allen <john.allen@xxxxxxx>
• Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v5 00/39] Shadow stacks for userspace
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [PATCH v6 2/3] cachestat: implement cachestat syscall
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Brian Foster <bfoster@xxxxxxxxxx>
• Re: [PATCH v5 00/39] Shadow stacks for userspace
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 39/39] x86/shstk: Add ARCH_SHSTK_STATUS
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 37/39] x86: Add PTRACE interface for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 31/39] x86/shstk: Introduce map_shadow_stack syscall
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 32/39] x86/shstk: Support WRSS for userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 29/39] x86/shstk: Introduce routines modifying shstk
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 27/39] x86/shstk: Add user-mode shadow stack support
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 26/39] x86: Introduce userspace API for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 25/39] mm: Warn on shadow stack memory in wrong vma
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 16/39] x86/mm: Check shadow stack page fault errors
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 02/39] x86/shstk: Add Kconfig option for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v5 01/39] Documentation/x86: Add CET shadow stack description
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• [PATCH v5 37/39] x86: Add PTRACE interface for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 36/39] x86/fpu: Add helper for initing features
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 33/39] x86: Expose thread features in /proc/$PID/status
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 28/39] x86/shstk: Handle thread shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 35/39] selftests/x86: Add shadow stack test
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 34/39] x86/shstk: Wire in shadow stack interface
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 30/39] x86/shstk: Handle signals for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 39/39] x86/shstk: Add ARCH_SHSTK_STATUS
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 29/39] x86/shstk: Introduce routines modifying shstk
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 32/39] x86/shstk: Support WRSS for userspace
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 31/39] x86/shstk: Introduce map_shadow_stack syscall
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 38/39] x86/shstk: Add ARCH_SHSTK_UNLOCK
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 27/39] x86/shstk: Add user-mode shadow stack support
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 24/39] x86/mm: Introduce MAP_ABOVE4G
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 26/39] x86: Introduce userspace API for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 25/39] mm: Warn on shadow stack memory in wrong vma
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 22/39] mm: Re-introduce vm_flags to do_mmap()
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 21/39] mm/mmap: Add shadow stack pages to memory accounting
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 20/39] mm: Add guard pages around a shadow stack.
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 17/39] x86/mm: Update maybe_mkwrite() for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 16/39] x86/mm: Check shadow stack page fault errors
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 15/39] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 13/39] x86/mm: Start actually marking _PAGE_COW
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 14/39] mm: Move VM_UFFD_MINOR_BIT from 37 to 38
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 07/39] x86: Add user control-protection fault handler
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 09/39] x86/mm: Move pmd_write(), pud_write() up in the file
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 02/39] x86/shstk: Add Kconfig option for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 01/39] Documentation/x86: Add CET shadow stack description
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v5 00/39] Shadow stacks for userspace
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: "Yann Droneaud" <ydroneaud@xxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v6 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v6 2/3] fanotify: define struct members to hold response decision context
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v6 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v6 1/3] fanotify: Ensure consistent variable type for response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v6 3/3] selftests: Add selftests for cachestat
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v6 2/3] cachestat: implement cachestat syscall
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• [PATCH v6 0/3] cachestat: a new syscall for page cache state of files
  • From: Nhat Pham <nphamcs@xxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Binbin Wu <binbin.wu@xxxxxxxxxxxxxxx>
• Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [RFC PATCH tip 2/2] sched/membarrier selftests: Fix: use KHDR_INCLUDES for kernel headers
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [RFC PATCH tip 1/2] rseq selftests: Fix: use KHDR_INCLUDES for kernel headers
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 8/9] KVM: Handle page fault for private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 7/9] KVM: Update lpage info when private/shared memory are mixed
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 4/9] KVM: Add KVM_EXIT_MEMORY_FAULT exit
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 7/9] KVM: Update lpage info when private/shared memory are mixed
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v5 7/8] LSM: wireup Linux Security Module syscalls
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/4] random: introduce getrandom() GRND_TIMESTAMP
  • From: Peter Lafreniere <peter@xxxxxxxx>
• Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 1/8] LSM: Identify modules by more than name
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: "Yann Droneaud" <ydroneaud@xxxxxxxxxx>
• Re: [PATCH v14 7/7] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 7/7] x86: vdso: Wire up getrandom() vDSO implementation
  • From: Christophe Leroy <christophe.leroy@xxxxxxxxxx>
• Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [RFC PATCH 4/4] testing: add a getrandom() GRND_TIMESTAMP vDSO demonstration/benchmark
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• [RFC PATCH 2/4] random: introduce generic vDSO getrandom(,, GRND_TIMESTAMP) fast path
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• [RFC PATCH 3/4] x86: vdso: Wire up getrandom() vDSO implementation.
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• [RFC PATCH 1/4] random: introduce getrandom() GRND_TIMESTAMP
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 1/8] LSM: Identify modules by more than name
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v14 0/7] implement getrandom() in vDSO
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 1/8] LSM: Identify modules by more than name
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script"
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script"
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data
  • From: kernel test robot <yujie.liu@xxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Vishal Annapurve <vannapurve@xxxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify, audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Dr. Greg" <greg@xxxxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• [PATCH v5 7/8] LSM: wireup Linux Security Module syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 8/8] LSM: selftests for Linux Security Module syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 6/8] LSM: lsm_set_self_attr syscall for LSM self attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 1/8] LSM: Identify modules by more than name
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 5/8] LSM: Create lsm_module_list system call
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 0/8] LSM: Three basic syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: minimum compiler for Linux UAPI (was Re: [PATCH v3] ethtool: Replace 0-length array with flexible array)
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Andy Lutomirski" <luto@xxxxxxxxxx>
• Re: minimum compiler for Linux UAPI (was Re: [PATCH v3] ethtool: Replace 0-length array with flexible array)
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v3] ethtool: Replace 0-length array with flexible array
  • From: Vincent MAILHOL <mailhol.vincent@xxxxxxxxxx>
• Re: [PATCH v3] ethtool: Replace 0-length array with flexible array
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Vishal Annapurve <vannapurve@xxxxxxxxxx>
• Re: [PATCH 05/30] selftests/rseq: Use ELF auxiliary vector for extensible rseq
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 05/30] selftests/rseq: Use ELF auxiliary vector for extensible rseq
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Jarkko Sakkinen <jarkko@xxxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 16/39] x86/mm: Check Shadow Stack page fault errors
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• [RFC PATCH v1] syscall_user_dispatch: ptrace SUSPEND feature for checkpoint/restore
  • From: Gregory Price <gourry.memverge@xxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH 05/30] selftests/rseq: Use ELF auxiliary vector for extensible rseq
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 05/30] selftests/rseq: Use ELF auxiliary vector for extensible rseq
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: [PATCH 02/30] rseq: Introduce feature size and alignment ELF auxiliary vector entries
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 02/30] rseq: Introduce feature size and alignment ELF auxiliary vector entries
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script"
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v4 16/39] x86/mm: Check Shadow Stack page fault errors
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v8 07/12] landlock: Add network rules support
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• RE: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: "Wang, Wei W" <wei.w.wang@xxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 2/8] LSM: Maintain a table of LSM attribute data
  • From: kernel test robot <yujie.liu@xxxxxxxxx>
• [RFC PATCH for tip] sched: Fix concurrency ID handling of usermodehelper kthreads
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v14 7/7] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v14 4/7] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>