Linux API

• Thread Index

• 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>
• [PATCH v14 5/7] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v14 6/7] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v14 3/7] x86: mm: Skip faulting instruction for VM_DROPPABLE faults
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v14 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v14 0/7] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v13 7/7] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v13 6/7] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH 21/21] xfs: enable atomic swapext feature
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 20/21] xfs: support non-power-of-two rtextsize with exchange-range
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 19/21] xfs: make atomic extent swapping support realtime files
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 18/21] xfs: condense symbolic links after an atomic swap
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 17/21] xfs: condense directories after an atomic swap
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 15/21] xfs: remove old swap extents implementation
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 16/21] xfs: condense extended attributes after an atomic swap
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 13/21] xfs: port xfs_swap_extent_forks to use xfs_swapext_req
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 14/21] xfs: allow xfs_swap_range to use older extent swap algorithms
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 12/21] xfs: consolidate all of the xfs_swap_extent_forks code
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 11/21] xfs: port xfs_swap_extents_rmap to our new code
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 10/21] xfs: add error injection to test swapext recovery
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 09/21] xfs: add a ->xchg_file_range handler
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 07/21] xfs: create deferred log items for extent swapping
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 08/21] xfs: enable xlog users to toggle atomic extent swapping
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 06/21] xfs: introduce a swap-extent log intent item
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 05/21] xfs: create a log incompat flag for atomic extent swapping
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 04/21] xfs: parameterize all the incompat log feature helpers
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 03/21] xfs: refactor non-power-of-two alignment checks
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 02/21] xfs: create a new helper to return a file's allocation unit
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 01/21] vfs: introduce new file range exchange ioctl
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCHSET v24.0 00/21] xfs: atomic file updates
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH v4 7/8] LSM: wireup Linux Security Module syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 8/8] LSM: selftests for Linux Security Module syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 6/8] LSM: lsm_set_self_attr syscall for LSM self attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 5/8] LSM: Create lsm_module_list system call
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 3/8] proc: Use lsmids instead of lsm names for attrs
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 2/8] LSM: Maintain a table of LSM attribute data
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 1/8] LSM: Identify modules by more than name
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v4 0/8] LSM: Three basic syscalls
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Chenyi Qiang <chenyi.qiang@xxxxxxxxx>
• Re: [PATCH v4 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@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: "Edgecombe, Rick P" <rick.p.edgecombe@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 v10 1/9] mm: Introduce memfd_restricted system call to create restricted user 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: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Huang, Kai" <kai.huang@xxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Richard Guy Briggs <rgb@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 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 v13 7/7] x86: vdso: Wire up getrandom() vDSO implementation
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v13 6/7] random: introduce generic vDSO getrandom() implementation
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v12 0/6] implement getrandom() in vDSO
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH] kernels/ksysfs.c: export kernel address bits
  • From: Thomas Weißschuh <linux@xxxxxxxxxxxxxx>
• Re: [PATCH v12 0/6] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 7/7] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 5/7] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 6/7] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 3/7] x86: mm: Skip faulting instruction for VM_DROPPABLE faults
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 4/7] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 2/7] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v13 0/7] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v12 0/6] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• 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: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 10/39] x86/mm: Introduce _PAGE_COW
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 1/3] fanotify: Ensure consistent variable type for response
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v4 10/39] x86/mm: Introduce _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 v12 0/6] implement getrandom() in vDSO
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v4 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v12 0/6] implement getrandom() in vDSO
  • From: Christophe Leroy <christophe.leroy@xxxxxxxxxx>
• Re: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Huang, Kai" <kai.huang@xxxxxxxxx>
• 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 2/9] KVM: Introduce per-page memory attributes
  • 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: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Borislav Petkov <bp@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: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Huang, Kai" <kai.huang@xxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • 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 6/9] KVM: Unmap existing mappings when change the memory attributes
  • 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 1/2] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH 2/2] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• 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: Borislav Petkov <bp@xxxxxxxxx>
• [PATCH for tip queue/sched/core] selftests/rseq: Add mm_numa_cid to test script
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH] mm/mempolicy: do not duplicate policy if it is not applicable for set_mempolicy_home_node
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxx>
• Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxx>
• Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: "Huang, Ying" <ying.huang@xxxxxxxxx>
• Re: [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [RFC PATCH] mm/mempolicy: Fix memory leak in set_mempolicy_home_node system call
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: "Huang, Kai" <kai.huang@xxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: "Huang, Kai" <kai.huang@xxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Xiaoyao Li <xiaoyao.li@xxxxxxxxx>
• Re: [PATCH RFC v12 2/6] x86: mm: Skip faulting instruction for VM_DROPPABLE faults
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v12 3/6] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v12 6/6] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v12 5/6] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v12 4/6] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH RFC v12 2/6] x86: mm: Skip faulting instruction for VM_DROPPABLE faults
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH RFC v12 1/6] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v12 0/6] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v5 3/3] fanotify,audit: Allow audit to use the full permission event response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v5 1/3] fanotify: Ensure consistent variable type for response
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v5 2/3] fanotify: define struct members to hold response decision context
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH v5 0/3] fanotify: Allow user space to pass back additional audit info
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v10 8/9] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 8/9] KVM: Handle page fault for private memory
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 5/9] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 8/9] KVM: Handle page fault for private memory
  • From: Yuan Yao <yuan.yao@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Yuan Yao <yuan.yao@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 8/9] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • 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 v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Xiaoyao Li <xiaoyao.li@xxxxxxxxx>
• Re: [PATCH v10 8/9] KVM: Handle page fault for private memory
  • From: Yuan Yao <yuan.yao@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 5/9] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 4/9] KVM: Add KVM_EXIT_MEMORY_FAULT exit
  • 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 2/9] KVM: Introduce per-page memory attributes
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • 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: [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [PATCH v10 6/9] KVM: Unmap existing mappings when change the memory attributes
  • From: Yuan Yao <yuan.yao@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 7/9] KVM: Update lpage info when private/shared memory are mixed
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v10 5/9] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v10 5/9] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 4/9] KVM: Add KVM_EXIT_MEMORY_FAULT exit
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 1/9] mm: Introduce memfd_restricted system call to create restricted user memory
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 2/9] KVM: Introduce per-page memory attributes
  • From: Fabiano Rosas <farosas@xxxxxxx>
• Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 7/9] KVM: Update lpage info when private/shared memory are mixed
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v10 5/9] KVM: Use gfn instead of hva for mmu_notifier_retry
  • 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 7/9] KVM: Update lpage info when private/shared memory are mixed
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v4 30/39] x86/shstk: Introduce map_shadow_stack syscall
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v10 5/9] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v8 08/12] landlock: Implement TCP network hooks
  • From: "Konstantin Meskhidze (A)" <konstantin.meskhidze@xxxxxxxxxx>
• [PATCH v11 4/4] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v11 3/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v11 2/4] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v11 1/4] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v11 0/4] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v3 5/9] LSM: lsm_get_self_attr syscall for LSM self attributes
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v4 33/39] x86: Prevent 32 bit operations for 64 bit shstk tasks
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description
  • From: Bagas Sanjaya <bagasdotme@xxxxxxxxx>
• Re: [PATCH v4 39/39] x86/shstk: Add ARCH_SHSTK_STATUS
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 38/39] x86/shstk: Add ARCH_SHSTK_UNLOCK
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 32/39] x86: Expose thread features in /proc/$PID/status
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 31/39] x86/shstk: Support wrss for userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 30/39] x86/shstk: Introduce map_shadow_stack syscall
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 29/39] x86/shstk: Handle signals for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 28/39] x86/shstk: Introduce routines modifying shstk
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 27/39] x86/shstk: Handle thread shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 26/39] x86/shstk: Add user-mode shadow stack support
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 25/39] x86: Introduce userspace API for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 24/39] mm: Warn on shadow stack memory in wrong vma
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 23/39] mm: Don't allow write GUPs to shadow stack memory
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 21/39] mm/mprotect: Exclude shadow stack from preserve_write
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 20/39] mm/mmap: Add shadow stack pages to memory accounting
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 18/39] mm: Fixup places that call pte_mkwrite() directly
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 17/39] x86/mm: Update maybe_mkwrite() for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 15/39] mm: Introduce VM_SHADOW_STACK for shadow stack memory
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 13/39] x86/mm: Start actually marking _PAGE_COW
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 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 v4 11/39] x86/mm: Update pte_modify for _PAGE_COW
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 10/39] x86/mm: Introduce _PAGE_COW
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 08/39] x86/mm: Remove _PAGE_DIRTY from kernel RO pages
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 07/39] x86: Add user control-protection fault handler
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 06/39] x86/fpu: Add helper for modifying xstate
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 05/39] x86/fpu/xstate: Introduce CET MSR and XSAVES supervisor states
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 04/39] x86/cpufeatures: Enable CET CR4 bit for shadow stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 03/39] x86/cpufeatures: Add CPU feature flags for shadow stacks
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 02/39] x86/shstk: Add Kconfig option for Shadow Stack
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v4 01/39] Documentation/x86: Add CET shadow stack description
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• [PATCH v4 34/39] x86/shstk: Wire in shadow stack interface
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 35/39] selftests/x86: Add shadow stack test
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 36/39] x86/fpu: Add helper for initing features
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 37/39] x86: Add PTRACE interface for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 38/39] x86/shstk: Add ARCH_SHSTK_UNLOCK
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 39/39] x86/shstk: Add ARCH_SHSTK_STATUS
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 30/39] x86/shstk: Introduce map_shadow_stack syscall
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 25/39] x86: Introduce userspace API for shadow stack
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>
• [PATCH v4 31/39] x86/shstk: Support wrss for userspace
  • From: Rick Edgecombe <rick.p.edgecombe@xxxxxxxxx>