Linux API

• Date Index

• Re: [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support, (continued)
  • Re: [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support, Edgecombe, Rick P
    • Re: [PATCH v6 29/41] x86/shstk: Add user-mode shadow stack support, Borislav Petkov
  • [PATCH v6 31/41] x86/shstk: Introduce routines modifying shstk, Rick Edgecombe
  • [PATCH v6 30/41] x86/shstk: Handle thread shadow stack, Rick Edgecombe
  • [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall, Rick Edgecombe
    • Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall, Deepak Gupta
      • Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall, Edgecombe, Rick P
        • Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall, Deepak Gupta
          • Re: [PATCH v6 33/41] x86/shstk: Introduce map_shadow_stack syscall, Edgecombe, Rick P
  • [PATCH v6 32/41] x86/shstk: Handle signals for shadow stack, Rick Edgecombe
  • [PATCH v6 34/41] x86/shstk: Support WRSS for userspace, Rick Edgecombe
  • [PATCH v6 35/41] x86: Expose thread features in /proc/$PID/status, Rick Edgecombe
  • [PATCH v6 36/41] x86/shstk: Wire in shadow stack interface, Rick Edgecombe
  • [PATCH v6 38/41] x86/fpu: Add helper for initing features, Rick Edgecombe
    • Re: [PATCH v6 38/41] x86/fpu: Add helper for initing features, Kees Cook
  • [PATCH v6 37/41] selftests/x86: Add shadow stack test, Rick Edgecombe
    • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, Kees Cook
    • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, David Hildenbrand
      • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, Edgecombe, Rick P
    • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, Borislav Petkov
      • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, Edgecombe, Rick P
        • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, Borislav Petkov
          • Re: [PATCH v6 37/41] selftests/x86: Add shadow stack test, Edgecombe, Rick P
  • [PATCH v6 40/41] x86/shstk: Add ARCH_SHSTK_UNLOCK, Rick Edgecombe
  • [PATCH v6 39/41] x86: Add PTRACE interface for shadow stack, Rick Edgecombe
  • [PATCH v6 41/41] x86/shstk: Add ARCH_SHSTK_STATUS, Rick Edgecombe
  • Re: [PATCH v6 00/41] Shadow stacks for userspace, Kees Cook
    • Re: [PATCH v6 00/41] Shadow stacks for userspace, Edgecombe, Rick P
  • Re: [PATCH v6 00/41] Shadow stacks for userspace, Mike Rapoport
    • Re: [PATCH v6 00/41] Shadow stacks for userspace, Edgecombe, Rick P
  • Re: [PATCH v6 00/41] Shadow stacks for userspace, John Allen
  • Re: [PATCH v6 00/41] Shadow stacks for userspace, Pengfei Xu
  • Re: [PATCH v6 00/41] Shadow stacks for userspace, Borislav Petkov
    • Re: [PATCH v6 00/41] Shadow stacks for userspace, Edgecombe, Rick P
• [RFC PATCH 0/2] Add flag as THP allocation hint for memfd_restricted() syscall, Ackerley Tng
  • [RFC PATCH 1/2] mm: restrictedmem: Add flag as THP allocation hint for memfd_restricted() syscall, Ackerley Tng
  • [RFC PATCH 2/2] selftests: restrictedmem: Add selftest for RMFD_HUGEPAGE, Ackerley Tng
  • Re: [RFC PATCH 0/2] Add flag as THP allocation hint for memfd_restricted() syscall, Yuan Yao
    • Re: [RFC PATCH 0/2] Add flag as THP allocation hint for memfd_restricted() syscall, Ackerley Tng
• [RFC PATCH 0/2] Providing mount for memfd_restricted() syscall, Ackerley Tng
  • [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted, Ackerley Tng
    • Re: [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted, Kirill A. Shutemov
      • Re: [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted, Ackerley Tng
        • Re: [RFC PATCH 1/2] mm: restrictedmem: Allow userspace to specify mount_path for memfd_restricted, kirill . shutemov
  • [RFC PATCH 2/2] selftests: restrictedmem: Check hugepage-ness of shmem file backing restrictedmem fd, Ackerley Tng
• [PATCH v2] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
  • Re: [PATCH v2] rseq.2: New man page for the rseq(2) API, Alex Colomar
    • Re: [PATCH v2] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
• [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
  • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Alejandro Colomar
    • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, G. Branden Robinson
      • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Alejandro Colomar
        • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, G. Branden Robinson
          • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Alejandro Colomar
            • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
      • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
        • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
        • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Alejandro Colomar
          • Re: [PATCH 1/1] rseq.2: New man page for the rseq(2) API, Mathieu Desnoyers
• copy on write for splice() from file to pipe?, Stefan Metzmacher
  • Re: copy on write for splice() from file to pipe?, Matthew Wilcox
    • Re: copy on write for splice() from file to pipe?, Stefan Metzmacher
  • Re: copy on write for splice() from file to pipe?, Linus Torvalds
    • Re: copy on write for splice() from file to pipe?, Stefan Metzmacher
      • Re: copy on write for splice() from file to pipe?, Linus Torvalds
        • Re: copy on write for splice() from file to pipe?, Linus Torvalds
          • Re: copy on write for splice() from file to pipe?, Jeremy Allison
          • Re: copy on write for splice() from file to pipe?, Stefan Metzmacher
            • Re: copy on write for splice() from file to pipe?, Linus Torvalds
    • Re: copy on write for splice() from file to pipe?, Dave Chinner
      • Re: copy on write for splice() from file to pipe?, Dave Chinner
        • Re: copy on write for splice() from file to pipe?, Matthew Wilcox
          • Re: copy on write for splice() from file to pipe?, Dave Chinner
            • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
              • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
                  • Re: copy on write for splice() from file to pipe?, Jeremy Allison
                    • Re: copy on write for splice() from file to pipe?, Stefan Metzmacher
                  • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                    • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
                      • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                        • Re: copy on write for splice() from file to pipe?, Jeremy Allison
                          • Re: copy on write for splice() from file to pipe?, Stefan Metzmacher
                          • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                            • Re: copy on write for splice() from file to pipe?, Stefan Metzmacher
                        • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                          • Re: copy on write for splice() from file to pipe?, Herbert Xu
                        • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
                          • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                            • Re: copy on write for splice() from file to pipe?, Jens Axboe
                              • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Ming Lei
                                • Re: copy on write for splice() from file to pipe?, Ming Lei
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Ming Lei
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                                • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                                • Re: copy on write for splice() from file to pipe?, Jens Axboe
        • Re: copy on write for splice() from file to pipe?, Linus Torvalds
          • Re: copy on write for splice() from file to pipe?, Dave Chinner
            • Re: copy on write for splice() from file to pipe?, Linus Torvalds
              • Re: copy on write for splice() from file to pipe?, Linus Torvalds
                • Re: copy on write for splice() from file to pipe?, Herbert Xu
              • RE: copy on write for splice() from file to pipe?, David Laight
                • Re: copy on write for splice() from file to pipe?, Jens Axboe
                • Re: copy on write for splice() from file to pipe?, Herbert Xu
            • Re: copy on write for splice() from file to pipe?, Herbert Xu
              • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
                • Re: copy on write for splice() from file to pipe?, Herbert Xu
                  • Re: copy on write for splice() from file to pipe?, Andy Lutomirski
                    • Re: copy on write for splice() from file to pipe?, Herbert Xu
• [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Richard Guy Briggs
  • [PATCH v7 1/3] fanotify: Ensure consistent variable type for response, Richard Guy Briggs
  • [PATCH v7 2/3] fanotify: define struct members to hold response decision context, Richard Guy Briggs
  • [PATCH v7 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
  • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Steve Grubb
  • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Jan Kara
    • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Paul Moore
      • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Jan Kara
        • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Paul Moore
          • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Steve Grubb
            • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Paul Moore
              • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Richard Guy Briggs
                • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Paul Moore
          • Re: [PATCH v7 0/3] fanotify: Allow user space to pass back additional audit info, Jan Kara
• [PATCH v9 0/3] cachestat: a new syscall for page cache state of files, Nhat Pham
  • [PATCH v9 1/3] workingset: refactor LRU refault to expose refault recency check, Nhat Pham
  • [PATCH v9 2/3] cachestat: implement cachestat syscall, Nhat Pham
    • Re: [PATCH v9 2/3] cachestat: implement cachestat syscall, kernel test robot
    • Re: [PATCH v9 2/3] cachestat: implement cachestat syscall, kernel test robot
    • Re: [PATCH v9 2/3] cachestat: implement cachestat syscall, kernel test robot
    • Re: [PATCH v9 2/3] cachestat: implement cachestat syscall, Arnd Bergmann
      • Re: [PATCH v9 2/3] cachestat: implement cachestat syscall, Nhat Pham
      • Message not available
        • Re: [PATCH v9 2/3] cachestat: implement cachestat syscall, Arnd Bergmann
  • [PATCH v9 3/3] selftests: Add selftests for cachestat, Nhat Pham
• [PATCH bpf-next v3 0/1] Document kfunc lifecycle / stability expectations, David Vernet
  • [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations, David Vernet
    • Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations, Alexei Starovoitov
    • Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations, patchwork-bot+netdevbpf
    • Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations, Cong Wang
      • Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations, Toke Høiland-Jørgensen
      • Re: [PATCH bpf-next v3] bpf/docs: Document kfunc lifecycle / stability expectations, David Vernet
• [PATCH v8 0/3] cachestat: a new syscall for page cache state of files, Nhat Pham
  • [PATCH v8 3/3] selftests: Add selftests for cachestat, Nhat Pham
  • [PATCH v8 1/3] workingset: refactor LRU refault to expose refault recency check, Nhat Pham
  • [PATCH v8 2/3] cachestat: implement cachestat syscall, Nhat Pham
    • Re: [PATCH v8 2/3] cachestat: implement cachestat syscall, Arnd Bergmann
      • Re: [PATCH v8 2/3] cachestat: implement cachestat syscall, Johannes Weiner
        • Re: [PATCH v8 2/3] cachestat: implement cachestat syscall, Arnd Bergmann
    • Re: [PATCH v8 2/3] cachestat: implement cachestat syscall, kernel test robot
• [PATCH v7 0/3] cachestat: a new syscall for page cache state of files, Nhat Pham
  • [PATCH v7 1/3] workingset: refactor LRU refault to expose refault recency check, Nhat Pham
    • Re: [PATCH v7 1/3] workingset: refactor LRU refault to expose refault recency check, Yu Zhao
      • Re: [PATCH v7 1/3] workingset: refactor LRU refault to expose refault recency check, Nhat Pham
  • [PATCH v7 2/3] cachestat: implement cachestat syscall, Nhat Pham
    • Re: [PATCH v7 2/3] cachestat: implement cachestat syscall, kernel test robot
      • Re: [PATCH v7 2/3] cachestat: implement cachestat syscall, Nhat Pham
      • [PATCH v7 2/3] cachestat: implement cachestat syscall, Nhat Pham
    • Re: [PATCH v7 2/3] cachestat: implement cachestat syscall, kernel test robot
  • [PATCH v7 3/3] selftests: Add selftests for cachestat, Nhat Pham
• [PATCH v5 00/39] Shadow stacks for userspace, Rick Edgecombe
  • [PATCH v5 01/39] Documentation/x86: Add CET shadow stack description, Rick Edgecombe
    • Re: [PATCH v5 01/39] Documentation/x86: Add CET shadow stack description, Kees Cook
  • [PATCH v5 02/39] x86/shstk: Add Kconfig option for shadow stack, Rick Edgecombe
    • Re: [PATCH v5 02/39] x86/shstk: Add Kconfig option for shadow stack, Kees Cook
  • [PATCH v5 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Rick Edgecombe
    • Re: [PATCH v5 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Kees Cook
  • [PATCH v5 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states, Rick Edgecombe
    • Re: [PATCH v5 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states, Kees Cook
  • [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate, Rick Edgecombe
    • Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate, Kees Cook
    • Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate, Borislav Petkov
      • Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate, Edgecombe, Rick P
        • Re: [PATCH v5 06/39] x86/fpu: Add helper for modifying xstate, Borislav Petkov
  • [PATCH v5 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack, Rick Edgecombe
    • Re: [PATCH v5 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack, Kees Cook
  • [PATCH v5 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages, Rick Edgecombe
    • Re: [PATCH v5 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages, Kees Cook
  • [PATCH v5 09/39] x86/mm: Move pmd_write(), pud_write() up in the file, Rick Edgecombe
  • [PATCH v5 07/39] x86: Add user control-protection fault handler, Rick Edgecombe
    • Re: [PATCH v5 07/39] x86: Add user control-protection fault handler, Kees Cook
    • Re: [PATCH v5 07/39] x86: Add user control-protection fault handler, Borislav Petkov
      • Re: [PATCH v5 07/39] x86: Add user control-protection fault handler, Edgecombe, Rick P
        • Re: [PATCH v5 07/39] x86: Add user control-protection fault handler, Borislav Petkov
          • Re: [PATCH v5 07/39] x86: Add user control-protection fault handler, Edgecombe, Rick P
            • Re: [PATCH v5 07/39] x86: Add user control-protection fault handler, Borislav Petkov
  • [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW, Kees Cook
    • Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW, David Hildenbrand
    • Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW, David Hildenbrand
      • Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW, Edgecombe, Rick P
        • Re: [PATCH v5 10/39] x86/mm: Introduce _PAGE_COW, David Hildenbrand
  • [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Kees Cook
    • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Borislav Petkov
      • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Edgecombe, Rick P
        • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Borislav Petkov
          • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Edgecombe, Rick P
            • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Borislav Petkov
              • Re: [PATCH v5 11/39] x86/mm: Update pte_modify for _PAGE_COW, Edgecombe, Rick P
  • [PATCH v5 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v5 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Kees Cook
  • [PATCH v5 14/39] mm: Move VM_UFFD_MINOR_BIT from 37 to 38, Rick Edgecombe
  • [PATCH v5 13/39] x86/mm: Start actually marking _PAGE_COW, Rick Edgecombe
  • [PATCH v5 15/39] mm: Introduce VM_SHADOW_STACK for shadow stack memory, Rick Edgecombe
  • [PATCH v5 16/39] x86/mm: Check shadow stack page fault errors, Rick Edgecombe
    • Re: [PATCH v5 16/39] x86/mm: Check shadow stack page fault errors, Kees Cook
  • [PATCH v5 17/39] x86/mm: Update maybe_mkwrite() for shadow stack, Rick Edgecombe
  • [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Rick Edgecombe
    • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
      • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
        • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
          • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
            • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
              • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                  • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
                    • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                      • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
                        • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                          • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
                            • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                              • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
                                • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                                • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
                • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
                  • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, Edgecombe, Rick P
                    • Re: [PATCH v5 18/39] mm: Handle faultless write upgrades for shstk, David Hildenbrand
  • [PATCH v5 20/39] mm: Add guard pages around a shadow stack., Rick Edgecombe
  • [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Rick Edgecombe
    • Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Kees Cook
    • Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Deepak Gupta
      • Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Edgecombe, Rick P
        • Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Deepak Gupta
          • Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Edgecombe, Rick P
            • Re: [PATCH v5 19/39] mm: Fixup places that call pte_mkwrite() directly, Deepak Gupta
  • [PATCH v5 21/39] mm/mmap: Add shadow stack pages to memory accounting, Rick Edgecombe
  • [PATCH v5 22/39] mm: Re-introduce vm_flags to do_mmap(), Rick Edgecombe
  • [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Rick Edgecombe
    • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, David Hildenbrand
      • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Florian Weimer
        • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Edgecombe, Rick P
          • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, David Hildenbrand
            • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Edgecombe, Rick P
              • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Kees Cook
                • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Edgecombe, Rick P
                  • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, David Hildenbrand
                    • Re: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Kees Cook
              • RE: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Schimpe, Christina
                • RE: [PATCH v5 23/39] mm: Don't allow write GUPs to shadow stack memory, Schimpe, Christina
  • [PATCH v5 25/39] mm: Warn on shadow stack memory in wrong vma, Rick Edgecombe
    • Re: [PATCH v5 25/39] mm: Warn on shadow stack memory in wrong vma, Kees Cook
  • [PATCH v5 26/39] x86: Introduce userspace API for shadow stack, Rick Edgecombe
    • Re: [PATCH v5 26/39] x86: Introduce userspace API for shadow stack, Kees Cook
  • [PATCH v5 24/39] x86/mm: Introduce MAP_ABOVE4G, Rick Edgecombe
  • [PATCH v5 27/39] x86/shstk: Add user-mode shadow stack support, Rick Edgecombe
    • Re: [PATCH v5 27/39] x86/shstk: Add user-mode shadow stack support, Kees Cook
  • [PATCH v5 38/39] x86/shstk: Add ARCH_SHSTK_UNLOCK, Rick Edgecombe
  • [PATCH v5 31/39] x86/shstk: Introduce map_shadow_stack syscall, Rick Edgecombe
    • Re: [PATCH v5 31/39] x86/shstk: Introduce map_shadow_stack syscall, Kees Cook
  • [PATCH v5 32/39] x86/shstk: Support WRSS for userspace, Rick Edgecombe
    • Re: [PATCH v5 32/39] x86/shstk: Support WRSS for userspace, Kees Cook
  • [PATCH v5 29/39] x86/shstk: Introduce routines modifying shstk, Rick Edgecombe
    • Re: [PATCH v5 29/39] x86/shstk: Introduce routines modifying shstk, Kees Cook
  • [PATCH v5 39/39] x86/shstk: Add ARCH_SHSTK_STATUS, Rick Edgecombe
    • Re: [PATCH v5 39/39] x86/shstk: Add ARCH_SHSTK_STATUS, Kees Cook
  • [PATCH v5 30/39] x86/shstk: Handle signals for shadow stack, Rick Edgecombe
  • [PATCH v5 34/39] x86/shstk: Wire in shadow stack interface, Rick Edgecombe
  • [PATCH v5 35/39] selftests/x86: Add shadow stack test, Rick Edgecombe
  • [PATCH v5 28/39] x86/shstk: Handle thread shadow stack, Rick Edgecombe
  • [PATCH v5 33/39] x86: Expose thread features in /proc/$PID/status, Rick Edgecombe
  • [PATCH v5 36/39] x86/fpu: Add helper for initing features, Rick Edgecombe
  • [PATCH v5 37/39] x86: Add PTRACE interface for shadow stack, Rick Edgecombe
    • Re: [PATCH v5 37/39] x86: Add PTRACE interface for shadow stack, Kees Cook
  • Re: [PATCH v5 00/39] Shadow stacks for userspace, Andrew Morton
    • Re: [PATCH v5 00/39] Shadow stacks for userspace, Edgecombe, Rick P
      • Re: [PATCH v5 00/39] Shadow stacks for userspace, Kees Cook
        • Re: [PATCH v5 00/39] Shadow stacks for userspace, Edgecombe, Rick P
  • Re: [PATCH v5 00/39] Shadow stacks for userspace, John Allen
  • Re: [PATCH v5 00/39] Shadow stacks for userspace, Mike Rapoport
• [PATCH v6 0/3] fanotify: Allow user space to pass back additional audit info, Richard Guy Briggs
  • [PATCH v6 1/3] fanotify: Ensure consistent variable type for response, Richard Guy Briggs
  • [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
    • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Steve Grubb
      • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Paul Moore
        • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
          • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Paul Moore
            • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Steve Grubb
    • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Paul Moore
      • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
        • Re: [PATCH v6 3/3] fanotify,audit: Allow audit to use the full permission event response, Paul Moore
  • [PATCH v6 2/3] fanotify: define struct members to hold response decision context, Richard Guy Briggs
  • Re: [PATCH v6 0/3] fanotify: Allow user space to pass back additional audit info, Jan Kara
• [PATCH v6 0/3] cachestat: a new syscall for page cache state of files, Nhat Pham
  • [PATCH v6 2/3] cachestat: implement cachestat syscall, Nhat Pham
    • Re: [PATCH v6 2/3] cachestat: implement cachestat syscall, Brian Foster
      • Re: [PATCH v6 2/3] cachestat: implement cachestat syscall, Nhat Pham
  • [PATCH v6 3/3] selftests: Add selftests for cachestat, Nhat Pham
  • [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Nhat Pham
    • Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Brian Foster
      • Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Johannes Weiner
        • Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Brian Foster
        • Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Yu Zhao
      • Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Nhat Pham
        • Re: [PATCH v6 1/3] workingset: refactor LRU refault to expose refault recency check, Brian Foster
• [RFC PATCH tip 1/2] rseq selftests: Fix: use KHDR_INCLUDES for kernel headers, Mathieu Desnoyers
  • [RFC PATCH tip 2/2] sched/membarrier selftests: Fix: use KHDR_INCLUDES for kernel headers, Mathieu Desnoyers
• [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, Yann Droneaud
  • [RFC PATCH 1/4] random: introduce getrandom() GRND_TIMESTAMP, Yann Droneaud
    • Re: [RFC PATCH 1/4] random: introduce getrandom() GRND_TIMESTAMP, Peter Lafreniere
  • [RFC PATCH 3/4] x86: vdso: Wire up getrandom() vDSO implementation., Yann Droneaud
  • [RFC PATCH 2/4] random: introduce generic vDSO getrandom(,, GRND_TIMESTAMP) fast path, Yann Droneaud
  • [RFC PATCH 4/4] testing: add a getrandom() GRND_TIMESTAMP vDSO demonstration/benchmark, Yann Droneaud
  • Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, Jason A. Donenfeld
  • Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, Yann Droneaud
    • Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, H. Peter Anvin
      • Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, Andy Lutomirski
        • Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, H. Peter Anvin
      • Re: [RFC PATCH 0/4] random: a simple vDSO mechanism for reseeding userspace CSPRNGs, Yann Droneaud
• [PATCH v5 0/8] LSM: Three basic syscalls, Casey Schaufler
  • [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data, Casey Schaufler
    • Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data, kernel test robot
    • Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data, Paul Moore
      • Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data, Casey Schaufler
        • Re: [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data, Paul Moore
  • [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs, Casey Schaufler
    • Re: [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs, Paul Moore
      • Re: [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs, Casey Schaufler
  • [PATCH v5 5/8] LSM: Create lsm_module_list system call, Casey Schaufler
    • Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call, kernel test robot
    • Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call, Paul Moore
      • Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call, Casey Schaufler
        • Re: [PATCH v5 5/8] LSM: Create lsm_module_list system call, Paul Moore
  • [PATCH v5 1/8] LSM: Identify modules by more than name, Casey Schaufler
    • Re: [PATCH v5 1/8] LSM: Identify modules by more than name, Paul Moore
      • Re: [PATCH v5 1/8] LSM: Identify modules by more than name, Casey Schaufler
        • Re: [PATCH v5 1/8] LSM: Identify modules by more than name, Paul Moore
  • [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Casey Schaufler
    • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Paul Moore
      • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Casey Schaufler
        • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Paul Moore
    • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Arnd Bergmann
      • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Paul Moore
        • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Mickaël Salaün
    • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Serge Hallyn (shallyn)
    • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Mickaël Salaün
      • Re: [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Casey Schaufler
  • [PATCH v5 6/8] LSM: lsm_set_self_attr syscall for LSM self attributes, Casey Schaufler
  • [PATCH v5 8/8] LSM: selftests for Linux Security Module syscalls, Casey Schaufler
  • [PATCH v5 7/8] LSM: wireup Linux Security Module syscalls, Casey Schaufler
    • Re: [PATCH v5 7/8] LSM: wireup Linux Security Module syscalls, Geert Uytterhoeven
• Re: [PATCH v3] ethtool: Replace 0-length array with flexible array, Jann Horn
  • Re: [PATCH v3] ethtool: Replace 0-length array with flexible array, Vincent MAILHOL
    • Re: minimum compiler for Linux UAPI (was Re: [PATCH v3] ethtool: Replace 0-length array with flexible array), Kees Cook
      • Re: minimum compiler for Linux UAPI (was Re: [PATCH v3] ethtool: Replace 0-length array with flexible array), Arnd Bergmann
• [RFC PATCH v1] syscall_user_dispatch: ptrace SUSPEND feature for checkpoint/restore, Gregory Price
• [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries, Mathieu Desnoyers
  • Re: [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries, Nathan Chancellor
    • Re: [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries, Peter Zijlstra
• [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script", Mathieu Desnoyers
  • Re: [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script", Peter Zijlstra
    • Re: [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script", Mathieu Desnoyers
• [RFC PATCH for tip] sched: Fix concurrency ID handling of usermodehelper kthreads, Mathieu Desnoyers
• [PATCH v14 0/7] implement getrandom() in vDSO, Jason A. Donenfeld
  • [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
    • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Ingo Molnar
      • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
        • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Ingo Molnar
          • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
      • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Andy Lutomirski
        • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
          • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Andy Lutomirski
        • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
          • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
            • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
              • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
                • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                  • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                  • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
                    • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Yann Droneaud
                      • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
                        • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                          • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                            • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
                            • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Andy Lutomirski
                              • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                                • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Dr. Greg
                              • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
                            • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Matthew Wilcox
                              • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                          • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
              • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Florian Weimer
                • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
                  • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Eric Biggers
                    • Re: [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Linus Torvalds
  • [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Jason A. Donenfeld
    • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Ingo Molnar
      • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Jason A. Donenfeld
        • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Ingo Molnar
          • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Borislav Petkov
            • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Jason A. Donenfeld
              • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Ingo Molnar
                • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Jason A. Donenfeld
                • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Ingo Molnar
                  • Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Jason A. Donenfeld
  • [PATCH v14 3/7] x86: mm: Skip faulting instruction for VM_DROPPABLE faults, Jason A. Donenfeld
  • [PATCH v14 6/7] random: introduce generic vDSO getrandom() implementation, Jason A. Donenfeld
  • [PATCH v14 5/7] arch: allocate vgetrandom_alloc() syscall number, Jason A. Donenfeld
  • [PATCH v14 4/7] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
  • [PATCH v14 7/7] x86: vdso: Wire up getrandom() vDSO implementation, Jason A. Donenfeld
    • Re: [PATCH v14 7/7] x86: vdso: Wire up getrandom() vDSO implementation, Christophe Leroy
      • Re: [PATCH v14 7/7] x86: vdso: Wire up getrandom() vDSO implementation, Jason A. Donenfeld
  • Re: [PATCH v14 0/7] implement getrandom() in vDSO, Mathieu Desnoyers
• [PATCHSET v24.0 00/21] xfs: atomic file updates, Darrick J. Wong
  • [PATCH 01/21] vfs: introduce new file range exchange ioctl, Darrick J. Wong
  • [PATCH 02/21] xfs: create a new helper to return a file's allocation unit, Darrick J. Wong
  • [PATCH 03/21] xfs: refactor non-power-of-two alignment checks, Darrick J. Wong
  • [PATCH 04/21] xfs: parameterize all the incompat log feature helpers, Darrick J. Wong
  • [PATCH 05/21] xfs: create a log incompat flag for atomic extent swapping, Darrick J. Wong
  • [PATCH 06/21] xfs: introduce a swap-extent log intent item, Darrick J. Wong
  • [PATCH 08/21] xfs: enable xlog users to toggle atomic extent swapping, Darrick J. Wong
  • [PATCH 07/21] xfs: create deferred log items for extent swapping, Darrick J. Wong
  • [PATCH 09/21] xfs: add a ->xchg_file_range handler, Darrick J. Wong
  • [PATCH 10/21] xfs: add error injection to test swapext recovery, Darrick J. Wong
  • [PATCH 11/21] xfs: port xfs_swap_extents_rmap to our new code, Darrick J. Wong
  • [PATCH 12/21] xfs: consolidate all of the xfs_swap_extent_forks code, Darrick J. Wong
  • [PATCH 14/21] xfs: allow xfs_swap_range to use older extent swap algorithms, Darrick J. Wong
  • [PATCH 13/21] xfs: port xfs_swap_extent_forks to use xfs_swapext_req, Darrick J. Wong
  • [PATCH 16/21] xfs: condense extended attributes after an atomic swap, Darrick J. Wong
  • [PATCH 15/21] xfs: remove old swap extents implementation, Darrick J. Wong
  • [PATCH 17/21] xfs: condense directories after an atomic swap, Darrick J. Wong
  • [PATCH 18/21] xfs: condense symbolic links after an atomic swap, Darrick J. Wong
  • [PATCH 19/21] xfs: make atomic extent swapping support realtime files, Darrick J. Wong
  • [PATCH 20/21] xfs: support non-power-of-two rtextsize with exchange-range, Darrick J. Wong
  • [PATCH 21/21] xfs: enable atomic swapext feature, Darrick J. Wong
• [PATCH v4 0/8] LSM: Three basic syscalls, Casey Schaufler
  • [PATCH v4 1/8] LSM: Identify modules by more than name, Casey Schaufler
  • [PATCH v4 2/8] LSM: Maintain a table of LSM attribute data, Casey Schaufler
    • Re: [PATCH v4 2/8] LSM: Maintain a table of LSM attribute data, kernel test robot
  • [PATCH v4 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes, Casey Schaufler
  • [PATCH v4 3/8] proc: Use lsmids instead of lsm names for attrs, Casey Schaufler
  • [PATCH v4 5/8] LSM: Create lsm_module_list system call, Casey Schaufler
  • [PATCH v4 6/8] LSM: lsm_set_self_attr syscall for LSM self attributes, Casey Schaufler
  • [PATCH v4 8/8] LSM: selftests for Linux Security Module syscalls, Casey Schaufler
  • [PATCH v4 7/8] LSM: wireup Linux Security Module syscalls, Casey Schaufler
• [PATCH] kernels/ksysfs.c: export kernel address bits, Thomas Weißschuh
• [PATCH v13 0/7] implement getrandom() in vDSO, Jason A. Donenfeld
  • [PATCH v13 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace, Jason A. Donenfeld
  • [PATCH v13 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
  • [PATCH v13 4/7] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
  • [PATCH v13 3/7] x86: mm: Skip faulting instruction for VM_DROPPABLE faults, Jason A. Donenfeld
  • [PATCH v13 6/7] random: introduce generic vDSO getrandom() implementation, Jason A. Donenfeld
    • Re: [PATCH v13 6/7] random: introduce generic vDSO getrandom() implementation, Eric Biggers
      • Re: [PATCH v13 6/7] random: introduce generic vDSO getrandom() implementation, Jason A. Donenfeld
  • [PATCH v13 5/7] arch: allocate vgetrandom_alloc() syscall number, Jason A. Donenfeld
  • [PATCH v13 7/7] x86: vdso: Wire up getrandom() vDSO implementation, Jason A. Donenfeld
    • Re: [PATCH v13 7/7] x86: vdso: Wire up getrandom() vDSO implementation, Eric Biggers
      • Re: [PATCH v13 7/7] x86: vdso: Wire up getrandom() vDSO implementation, Jason A. Donenfeld
• [PATCH 1/2] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Mathieu Desnoyers
  • [PATCH 2/2] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node, Mathieu Desnoyers
• [PATCH for tip queue/sched/core] selftests/rseq: Add mm_numa_cid to test script, Mathieu Desnoyers
• [PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Mathieu Desnoyers
• [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Mathieu Desnoyers
  • Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Randy Dunlap
  • Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Huang, Ying
  • Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Michal Hocko
    • Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Aneesh Kumar K.V
    • Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Mathieu Desnoyers
      • [PATCH] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node, Michal Hocko
        • Re: [PATCH] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node, Mathieu Desnoyers
  • Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call, Aneesh Kumar K.V
• [PATCH v12 0/6] implement getrandom() in vDSO, Jason A. Donenfeld
  • [PATCH RFC v12 1/6] mm: add VM_DROPPABLE for designating always lazily freeable mappings, Jason A. Donenfeld
  • [PATCH RFC v12 2/6] x86: mm: Skip faulting instruction for VM_DROPPABLE faults, Jason A. Donenfeld
    • Re: [PATCH RFC v12 2/6] x86: mm: Skip faulting instruction for VM_DROPPABLE faults, Jason A. Donenfeld
  • [PATCH v12 4/6] arch: allocate vgetrandom_alloc() syscall number, Jason A. Donenfeld
  • [PATCH v12 5/6] random: introduce generic vDSO getrandom() implementation, Jason A. Donenfeld
  • [PATCH v12 6/6] x86: vdso: Wire up getrandom() vDSO implementation, Jason A. Donenfeld
  • [PATCH v12 3/6] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
  • Re: [PATCH v12 0/6] implement getrandom() in vDSO, Christophe Leroy
    • Re: [PATCH v12 0/6] implement getrandom() in vDSO, Eric Biggers
      • Re: [PATCH v12 0/6] implement getrandom() in vDSO, Jason A. Donenfeld
        • Re: [PATCH v12 0/6] implement getrandom() in vDSO, Eric Biggers
    • Re: [PATCH v12 0/6] implement getrandom() in vDSO, Jason A. Donenfeld
• [PATCH v5 0/3] fanotify: Allow user space to pass back additional audit info, Richard Guy Briggs
  • [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Richard Guy Briggs
    • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Jan Kara
      • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Paul Moore
        • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Jan Kara
      • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Richard Guy Briggs
        • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Jan Kara
          • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Richard Guy Briggs
            • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Jan Kara
              • Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context, Richard Guy Briggs
  • [PATCH v5 1/3] fanotify: Ensure consistent variable type for response, Richard Guy Briggs
    • Re: [PATCH v5 1/3] fanotify: Ensure consistent variable type for response, Paul Moore
  • [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
    • Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Paul Moore
      • Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
        • Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Paul Moore
    • Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Steve Grubb
      • Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Richard Guy Briggs
        • Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response, Steve Grubb
          • Re: [PATCH v5 3/3] fanotify, audit: Allow audit to use the full permission event response, Richard Guy Briggs
• [PATCH v11 0/4] implement getrandom() in vDSO, Jason A. Donenfeld
  • [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
    • Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Florian Weimer
      • Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
    • Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Jann Horn
      • Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
        • Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Florian Weimer
          • Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall, Jason A. Donenfeld
  • [PATCH v11 2/4] arch: allocate vgetrandom_alloc() syscall number, Jason A. Donenfeld
  • [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation, Jason A. Donenfeld
    • Re: [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation, Florian Weimer
      • Re: [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation, Jason A. Donenfeld
        • Re: [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation, Florian Weimer
  • [PATCH v11 4/4] x86: vdso: Wire up getrandom() vDSO implementation, Jason A. Donenfeld
• [PATCH v4 00/39] Shadow stacks for userspace, Rick Edgecombe
  • [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description, Rick Edgecombe
    • Re: [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description, Kees Cook
    • Re: [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description, Bagas Sanjaya
      • Re: [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description, Edgecombe, Rick P
  • [PATCH v4 02/39] x86/shstk: Add Kconfig option for Shadow Stack, Rick Edgecombe
    • Re: [PATCH v4 02/39] x86/shstk: Add Kconfig option for Shadow Stack, Kees Cook
  • [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Rick Edgecombe
    • Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Kees Cook
    • Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Borislav Petkov
      • Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Edgecombe, Rick P
        • Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks, Borislav Petkov
  • [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states, Rick Edgecombe
    • Re: [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states, Kees Cook
    • Re: [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states, Borislav Petkov
      • Re: [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states, Edgecombe, Rick P
  • [PATCH v4 07/39] x86: Add user control-protection fault handler, Rick Edgecombe
    • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Kees Cook
    • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Borislav Petkov
      • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Edgecombe, Rick P
        • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Borislav Petkov
          • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Edgecombe, Rick P
            • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Borislav Petkov
    • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Borislav Petkov
      • Re: [PATCH v4 07/39] x86: Add user control-protection fault handler, Edgecombe, Rick P
  • [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack, Rick Edgecombe
    • Re: [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack, Kees Cook
    • Re: [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack, Borislav Petkov
      • Re: [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack, Edgecombe, Rick P
  • [PATCH v4 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages, Rick Edgecombe
    • Re: [PATCH v4 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages, Kees Cook
    • Re: [PATCH v4 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages, Borislav Petkov
  • [PATCH v4 09/39] x86/mm: Move pmd_write(), pud_write() up in the file, Rick Edgecombe
  • [PATCH v4 10/39] x86/mm: Introduce _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v4 10/39] x86/mm: Introduce _PAGE_COW, Kees Cook
    • Re: [PATCH v4 10/39] x86/mm: Introduce _PAGE_COW, Borislav Petkov
      • Re: [PATCH v4 10/39] x86/mm: Introduce _PAGE_COW, Edgecombe, Rick P
  • [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate, Rick Edgecombe
    • Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate, Kees Cook
    • Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate, Borislav Petkov
      • Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate, Edgecombe, Rick P
        • Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate, Borislav Petkov
  • [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW, Kees Cook
    • Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW, Borislav Petkov
      • Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW, Edgecombe, Rick P
        • Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW, Borislav Petkov
          • Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW, Edgecombe, Rick P
  • [PATCH v4 16/39] x86/mm: Check Shadow Stack page fault errors, Rick Edgecombe
    • Re: [PATCH v4 16/39] x86/mm: Check Shadow Stack page fault errors, Borislav Petkov
      • Re: [PATCH v4 16/39] x86/mm: Check Shadow Stack page fault errors, Edgecombe, Rick P
  • [PATCH v4 18/39] mm: Fixup places that call pte_mkwrite() directly, Rick Edgecombe
    • Re: [PATCH v4 18/39] mm: Fixup places that call pte_mkwrite() directly, Kees Cook
  • [PATCH v4 13/39] x86/mm: Start actually marking _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v4 13/39] x86/mm: Start actually marking _PAGE_COW, Kees Cook
  • [PATCH v4 14/39] mm: Move VM_UFFD_MINOR_BIT from 37 to 38, Rick Edgecombe
  • [PATCH v4 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Rick Edgecombe
    • Re: [PATCH v4 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Kees Cook
    • Re: [PATCH v4 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Borislav Petkov
      • Re: [PATCH v4 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Edgecombe, Rick P
        • Re: [PATCH v4 12/39] x86/mm: Update ptep_set_wrprotect() and pmdp_set_wrprotect() for transition from _PAGE_DIRTY to _PAGE_COW, Borislav Petkov
  • [PATCH v4 17/39] x86/mm: Update maybe_mkwrite() for shadow stack, Rick Edgecombe
    • Re: [PATCH v4 17/39] x86/mm: Update maybe_mkwrite() for shadow stack, Kees Cook
  • [PATCH v4 15/39] mm: Introduce VM_SHADOW_STACK for shadow stack memory, Rick Edgecombe
    • Re: [PATCH v4 15/39] mm: Introduce VM_SHADOW_STACK for shadow stack memory, Kees Cook
  • [PATCH v4 21/39] mm/mprotect: Exclude shadow stack from preserve_write, Rick Edgecombe
    • Re: [PATCH v4 21/39] mm/mprotect: Exclude shadow stack from preserve_write, Kees Cook
  • [PATCH v4 22/39] mm: Re-introduce vm_flags to do_mmap(), Rick Edgecombe
  • [PATCH v4 19/39] mm: Add guard pages around a shadow stack., Rick Edgecombe
  • [PATCH v4 20/39] mm/mmap: Add shadow stack pages to memory accounting, Rick Edgecombe
    • Re: [PATCH v4 20/39] mm/mmap: Add shadow stack pages to memory accounting, Kees Cook
  • [PATCH v4 23/39] mm: Don't allow write GUPs to shadow stack memory, Rick Edgecombe
    • Re: [PATCH v4 23/39] mm: Don't allow write GUPs to shadow stack memory, Kees Cook
  • [PATCH v4 24/39] mm: Warn on shadow stack memory in wrong vma, Rick Edgecombe
    • Re: [PATCH v4 24/39] mm: Warn on shadow stack memory in wrong vma, Kees Cook
  • [PATCH v4 28/39] x86/shstk: Introduce routines modifying shstk, Rick Edgecombe
    • Re: [PATCH v4 28/39] x86/shstk: Introduce routines modifying shstk, Kees Cook
  • [PATCH v4 27/39] x86/shstk: Handle thread shadow stack, Rick Edgecombe
    • Re: [PATCH v4 27/39] x86/shstk: Handle thread shadow stack, Kees Cook
  • [PATCH v4 29/39] x86/shstk: Handle signals for shadow stack, Rick Edgecombe
    • Re: [PATCH v4 29/39] x86/shstk: Handle signals for shadow stack, Kees Cook
  • [PATCH v4 32/39] x86: Expose thread features in /proc/$PID/status, Rick Edgecombe
    • Re: [PATCH v4 32/39] x86: Expose thread features in /proc/$PID/status, Kees Cook
  • [PATCH v4 26/39] x86/shstk: Add user-mode shadow stack support, Rick Edgecombe
    • Re: [PATCH v4 26/39] x86/shstk: Add user-mode shadow stack support, Kees Cook
  • [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks, Rick Edgecombe
    • Re: [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks, Andy Lutomirski
      • Re: [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks, Edgecombe, Rick P
        • Re: [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks, Edgecombe, Rick P
  • [PATCH v4 31/39] x86/shstk: Support wrss for userspace, Rick Edgecombe
    • Re: [PATCH v4 31/39] x86/shstk: Support wrss for userspace, Kees Cook
  • [PATCH v4 25/39] x86: Introduce userspace API for shadow stack, Rick Edgecombe
    • Re: [PATCH v4 25/39] x86: Introduce userspace API for shadow stack, Kees Cook
  • [PATCH v4 30/39] x86/shstk: Introduce map_shadow_stack syscall, Rick Edgecombe
    • Re: [PATCH v4 30/39] x86/shstk: Introduce map_shadow_stack syscall, Kees Cook
      • Re: [PATCH v4 30/39] x86/shstk: Introduce map_shadow_stack syscall, Edgecombe, Rick P
  • [PATCH v4 39/39] x86/shstk: Add ARCH_SHSTK_STATUS, Rick Edgecombe
    • Re: [PATCH v4 39/39] x86/shstk: Add ARCH_SHSTK_STATUS, Kees Cook
  • [PATCH v4 38/39] x86/shstk: Add ARCH_SHSTK_UNLOCK, Rick Edgecombe
    • Re: [PATCH v4 38/39] x86/shstk: Add ARCH_SHSTK_UNLOCK, Kees Cook
  • [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack, Rick Edgecombe
    • Re: [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack, Kees Cook
    • Re: [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack, Mike Rapoport
      • Re: [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack, Edgecombe, Rick P
  • [PATCH v4 36/39] x86/fpu: Add helper for initing features, Rick Edgecombe
  • [PATCH v4 35/39] selftests/x86: Add shadow stack test, Rick Edgecombe
  • [PATCH v4 34/39] x86/shstk: Wire in shadow stack interface, Rick Edgecombe
• [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM, Chao Peng
  • [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Fuad Tabba
      • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Huang, Kai
      • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
        • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Huang, Kai
          • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
            • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Huang, Kai
              • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
                • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Huang, Kai
                  • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
                  • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Vlastimil Babka
                    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Kirill A. Shutemov
                      • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Vlastimil Babka
                    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Huang, Kai
                      • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Sean Christopherson
                        • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Vlastimil Babka
                • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Sean Christopherson
                  • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Huang, Kai
                  • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
                  • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Kirill A. Shutemov
                    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Vlastimil Babka
                    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Michael Roth
    • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Sean Christopherson
      • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
        • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Sean Christopherson
          • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Chao Peng
            • Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory, Isaku Yamahata