Linux API

• Thread Index

• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH RESEND] Add sicode to /proc/<PID>/stat.
  • From: Florian Mayer <fmayer@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A . Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH RESEND] Add sicode to /proc/<PID>/stat.
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Andy Lutomirski" <luto@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A . Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Chuck Lever III <chuck.lever@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH v7 05/14] mm/memfd: Introduce MFD_INACCESSIBLE flag
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• [PATCH mm-unstable v3 04/10] mm/khugepaged: add tracepoint to hpage_collapse_scan_file()
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 10/10] selftests/vm: add selftest for MADV_COLLAPSE of uffd-minor memory
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 02/10] mm/khugepaged: attempt to map file/shmem-backed pte-mapped THPs by pmds
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 09/10] selftests/vm: add file/shmem MADV_COLLAPSE selftest for cleared pmd
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 07/10] selftests/vm: add thp collapse file and tmpfs testing
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 08/10] selftests/vm: add thp collapse shmem testing
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 05/10] selftests/vm: dedup THP helpers
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 06/10] selftests/vm: modularize thp collapse memory operations
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 03/10] mm/madvise: add file and shmem support to MADV_COLLAPSE
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 01/10] mm/shmem: add flag to enforce shmem THP in hugepage_vma_check()
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v3 00/10] mm: add file/shmem support to MADV_COLLAPSE
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jan Kara <jack@xxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: "NeilBrown" <neilb@xxxxxxx>
• [PATCH v4 5/6] nfs: report the inode version in statx if requested
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v4 6/6] ceph: fill in the change attribute in statx requests
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v4 3/6] ext4: unconditionally enable the i_version counter
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v4 2/6] ext4: fix i_version handling in ext4
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v4 4/6] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v4 1/6] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v4 0/6] vfs: clean up i_version behavior and expose it via statx
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v5 1/8] statx: add direct I/O alignment information
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [man-pages RFC PATCH v3] statx, inode: document the STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v5 8/8] xfs: support STATX_DIOALIGN
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A . Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [RFC PATCH v2] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re:
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re:
  • From: Yang Shi <shy828301@xxxxxxxxx>
• Re: [RFC PATCH 2/2] fs/xattr: wire up syscalls
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A . Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] fs/xattr: wire up syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• [RFC PATCH 2/2] fs/xattr: wire up syscalls
  • From: Christian Göttsche <cgzones@xxxxxxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH v5 7/8] f2fs: support STATX_DIOALIGN
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v5 5/8] f2fs: move f2fs_force_buffered_io() into file.c
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v5 6/8] f2fs: simplify f2fs_force_buffered_io()
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/7] ext4: unconditionally enable the i_version counter
  • From: Jan Kara <jack@xxxxxxx>
• Re: [man-pages PATCH] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [man-pages PATCH] statx, inode: document the new STATX_INO_VERSION field
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v5 8/8] xfs: support STATX_DIOALIGN
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v4 0/9] make statx() return DIO alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 7/8] f2fs: support STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 5/8] f2fs: move f2fs_force_buffered_io() into file.c
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 8/8] xfs: support STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 4/8] ext4: support STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 3/8] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 6/8] f2fs: simplify f2fs_force_buffered_io()
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 0/8] make statx() return DIO alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 1/8] statx: add direct I/O alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH mm-unstable v2 3/9] mm/madvise: add file and shmem support to MADV_COLLAPSE
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 9/9] selftests/vm: add selftest for MADV_COLLAPSE of uffd-minor memory
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 5/9] selftests/vm: dedup THP helpers
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 6/9] selftests/vm: modularize thp collapse memory operations
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 8/9] selftests/vm: add thp collapse shmem testing
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 4/9] mm/khugepaged: add tracepoint to hpage_collapse_scan_file()
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 1/9] mm/shmem: add flag to enforce shmem THP in hugepage_vma_check()
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 7/9] selftests/vm: add thp collapse file and tmpfs testing
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable v2 2/9] mm/khugepaged: attempt to map file/shmem-backed pte-mapped THPs by pmds
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [no subject]
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH v3 7/7] ceph: fill in the change attribute in statx requests
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 6/7] nfs: report the inode version in statx if requested
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [man-pages PATCH] statx, inode: document the new STATX_INO_VERSION field
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 5/7] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 4/7] xfs: don't bump the i_version on an atime update in xfs_vn_update_time
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 3/7] ext4: unconditionally enable the i_version counter
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 2/7] ext4: fix i_version handling in ext4
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 1/7] iversion: update comments with info about atime updates
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH v3 0/7] vfs: clean up i_version behavior and expose it via statx
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v4 0/9] make statx() return DIO alignment information
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Fuad Tabba <tabba@xxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: "Colin Walters" <walters@xxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: "Colin Walters" <walters@xxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• RE: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• RE: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Xi Ruoyao <xry111@xxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Xi Ruoyao <xry111@xxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>
• [PATCH v3] Many pages: Document fixed-width types with ISO C naming
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [RFC PATCH] f*xattr: allow O_PATH descriptors
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Vishal Annapurve <vannapurve@xxxxxxxxxx>
• Re: [RFC PATCH] f*xattr: allow O_PATH descriptors
  • From: Christian Göttsche <cgzones@xxxxxxxxxxxxxx>
• [PATCH] vfs: report an inode version in statx for IS_I_VERSION inodes
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A . Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Hugh Dickins <hughd@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v4] MIPS: Expose prid and globalnumber to sysfs
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH v4] MIPS: Expose prid and globalnumber to sysfs
  • From: "Jiaxun Yang" <jiaxun.yang@xxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Kirill A . Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [PATCH v4] MIPS: Expose prid and globalnumber to sysfs
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v4] MIPS: Expose prid and globalnumber to sysfs
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH v4] MIPS: Expose prid and globalnumber to sysfs
  • From: Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx>
• Re: [PATCH v3] MIPS: Expose prid and globalnumber to sysfs
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH mm-unstable 3/9] mm/madvise: add file and shmem support to MADV_COLLAPSE
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH v3] MIPS: Expose prid and globalnumber to sysfs
  • From: Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH mm-unstable 3/9] mm/madvise: add file and shmem support to MADV_COLLAPSE
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH mm-unstable 3/9] mm/madvise: add file and shmem support to MADV_COLLAPSE
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2] kernel/sys_ni: add compat entry for fadvise64_64
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2] kernel/sys_ni: add compat entry for fadvise64_64
  • From: <Conor.Dooley@xxxxxxxxxxxxx>
• Re: [PATCH v2] MIPS: Expose prid and globalnumber to sysfs
  • From: Florian Fainelli <f.fainelli@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v2] MIPS: Expose prid and globalnumber to sysfs
  • From: Florian Fainelli <f.fainelli@xxxxxxxxx>
• [PATCH mm-unstable 6/9] selftests/vm: modularize thp collapse memory operations
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 9/9] selftests/vm: add selftest for MADV_COLLAPSE of uffd-minor memory
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 7/9] selftests/vm: add thp collapse file and tmpfs testing
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 8/9] selftests/vm: add thp collapse shmem testing
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 5/9] selftests/vm: dedup THP helpers
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 4/9] mm/khugepaged: add tracepoint to hpage_collapse_scan_file()
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 3/9] mm/madvise: add file and shmem support to MADV_COLLAPSE
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 2/9] mm/khugepaged: attempt to map file/shmem-backed pte-mapped THPs by pmds
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 1/9] mm/shmem: add flag to enforce shmem THP in hugepage_vma_check()
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• [PATCH mm-unstable 0/9] mm: add file/shmem support to MADV_COLLAPSE
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 05/14] mm/memfd: Introduce MFD_INACCESSIBLE flag
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: Quentin Perret <qperret@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v2] MIPS: Expose prid and globalnumber to sysfs
  • From: Greg KH <greg@xxxxxxxxx>
• [PATCH v2] MIPS: Expose prid and globalnumber to sysfs
  • From: Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• Re: [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v3 02/23] rseq: Introduce extensible rseq ABI
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [RFC][PATCH] uapi: Remove the inclusion of linux/mount.h from uapi/linux/fs.h
  • From: Ian Kent <raven@xxxxxxxxxx>
• Re: [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 05/14] mm/memfd: Introduce MFD_INACCESSIBLE flag
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 05/14] mm/memfd: Introduce MFD_INACCESSIBLE flag
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [RFC][PATCH] uapi: Remove the inclusion of linux/mount.h from uapi/linux/fs.h
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: "Peter.Enderborg@xxxxxxxx" <Peter.Enderborg@xxxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH 0/5] Add process_memwatch syscall
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• Re: [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 08/14] KVM: Rename mmu_notifier_*
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 02/23] rseq: Introduce extensible rseq ABI
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v4 0/4] fanotify: Allow user space to pass back additional audit info
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [RFC][PATCH] uapi: Remove the inclusion of linux/mount.h from uapi/linux/fs.h
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH] MIPS: Expose prid and globalnumber to sysfs
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] MIPS: Expose prid and globalnumber to sysfs
  • From: Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx>
• Re: [RFC][PATCH] uapi: Remove the inclusion of linux/mount.h from uapi/linux/fs.h
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [RFC][PATCH] uapi: Remove the inclusion of linux/mount.h from uapi/linux/fs.h
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH v2] kernel/sys_ni: add compat entry for fadvise64_64
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH v2] kernel/sys_ni: add compat entry for fadvise64_64
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v7 08/14] KVM: Rename mmu_notifier_*
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v7 05/14] mm/memfd: Introduce MFD_INACCESSIBLE flag
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 02/14] selftests/memfd: Add tests for F_SEAL_AUTO_ALLOCATE
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH mm-unstable] mm/madvise: remove CAP_SYS_ADMIN requirement for process_madvise(MADV_COLLAPSE)
  • From: Yang Shi <shy828301@xxxxxxxxx>
• Re: [PATCH v3 00/23] RSEQ node id and virtual cpu id extensions
  • From: Chris Kennelly <ckennelly@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 09/14] KVM: Extend the memslot to support fd-based private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 08/14] KVM: Rename mmu_notifier_*
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 09/14] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 14/14] memfd_create.2: Describe MFD_INACCESSIBLE flag
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 12/14] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 00/23] RSEQ node id and virtual cpu id extensions
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH mm-unstable] mm/madvise: remove CAP_SYS_ADMIN requirement for process_madvise(MADV_COLLAPSE)
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re: [PATCH v3 00/23] RSEQ node id and virtual cpu id extensions
  • From: Peter Oskolkov <posk@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v3 00/23] RSEQ node id and virtual cpu id extensions
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH mm-unstable] mm/madvise: remove CAP_SYS_ADMIN requirement for process_madvise(MADV_COLLAPSE)
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH mm-unstable] mm/madvise: remove CAP_SYS_ADMIN requirement for process_madvise(MADV_COLLAPSE)
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re: [PATCH mm-unstable] mm/madvise: remove CAP_SYS_ADMIN requirement for process_madvise(MADV_COLLAPSE)
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• [PATCH mm-unstable] mm/madvise: remove CAP_SYS_ADMIN requirement for process_madvise(MADV_COLLAPSE)
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re: [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v3 00/23] RSEQ node id and virtual cpu id extensions
  • From: Peter Oskolkov <posk@xxxxxxx>
• Re: [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v7 14/14] memfd_create.2: Describe MFD_INACCESSIBLE flag
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: [PATCH v7 12/14] KVM: Handle page fault for private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 09/14] KVM: Extend the memslot to support fd-based private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• [PATCH v3 22/23] selftests/rseq: x86: Implement rseq_load_u32_u32
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 14/23] selftests/rseq: arm: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 21/23] selftests/rseq: parametrized vm_vcpu_id test
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 23/23] selftests/rseq: Implement numa node id vs vm_vcpu_id invariant test
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 19/23] selftests/rseq: riscv: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 16/23] selftests/rseq: mips: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 17/23] selftests/rseq: ppc: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 18/23] selftests/rseq: s390: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 20/23] selftests/rseq: basic percpu ops vm_vcpu_id test
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 13/23] selftests/rseq: x86: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 15/23] selftests/rseq: arm64: Template memory ordering and percpu access mode
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 12/23] selftests/rseq: Implement rseq vm_vcpu_id field support
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 09/23] sched: Introduce per memory space current virtual cpu id
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 10/23] rseq: extend struct rseq with per memory space vcpu id
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 11/23] selftests/rseq: Remove RSEQ_SKIP_FASTPATH code
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 08/23] cpumask: implement cpumask_{first,next}_{zero,one}_and_zero
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 06/23] lib: invert _find_next_bit source arguments
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 07/23] lib: implement find_{first,next}_{zero,one}_and_zero_bit
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 05/23] selftests/rseq: Implement rseq numa node id field selftest
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 04/23] selftests/rseq: Use ELF auxiliary vector for extensible rseq
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 02/23] rseq: Introduce extensible rseq ABI
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 00/23] RSEQ node id and virtual cpu id extensions
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 03/23] rseq: extend struct rseq with numa node id
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH v3 01/23] rseq: Introduce feature size and alignment ELF auxiliary vector entries
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v7 08/14] KVM: Rename mmu_notifier_*
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Jim Baxter <jim_baxter@xxxxxxxxxx>
• Re: [RFC] futex2: add NUMA awareness
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/2] rseq: Deprecate RSEQ_CS_FLAG_NO_RESTART_ON_* flags
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH 3/5] mm: wire up process_memwatch syscall for x86
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• [PATCH 5/5] mm: add process_memwatch syscall documentation
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• [PATCH 4/5] selftests: vm: add process_memwatch syscall tests
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• [PATCH 2/5] mm: Implement process_memwatch syscall
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• [PATCH 1/5] fs/proc/task_mmu: make functions global to be used in other files
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• [PATCH 0/5] Add process_memwatch syscall
  • From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v5 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation/filesystems/proc.rst: document procfs inode timestamps
  • From: Muchun Song <songmuchun@xxxxxxxxxxxxx>
• Re: [PATCH v5 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation/filesystems/proc.rst: document procfs inode timestamps
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH v4 1/9] statx: add direct I/O alignment information
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH v5] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v4 4/9] ext4: support STATX_DIOALIGN
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC] futex2: add NUMA awareness
  • From: Andrey Semashev <andrey.semashev@xxxxxxxxx>
• Re: [PATCH v4 1/9] statx: add direct I/O alignment information
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [man-pages RFC PATCH v2] statx.2, open.2: document STATX_DIOALIGN
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 1/2] Documentation/filesystems/proc.rst: remove ancient boiler plate
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• [PATCH 2/2] Documentation/filesystems/proc.rst: document procfs inode timestamps
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• [PATCH 0/2] procfs: document proc timestamps
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: [PATCH v4 9/9] xfs: support STATX_DIOALIGN
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [RFC] proc: fix create timestamp of files in proc
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: [PATCH v5] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC] proc: fix create timestamp of files in proc
  • From: Yuchen Zhang <zhangyuchen.lcr@xxxxxxxxxxxxx>
• Re: [PATCH v4 9/9] xfs: support STATX_DIOALIGN
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v4 3/9] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [man-pages RFC PATCH v2] statx.2, open.2: document STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 8/9] f2fs: support STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 0/9] make statx() return DIO alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 9/9] xfs: support STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 2/9] vfs: support STATX_DIOALIGN on block devices
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 7/9] f2fs: simplify f2fs_force_buffered_io()
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 3/9] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 5/9] f2fs: move f2fs_force_buffered_io() into file.c
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 1/9] statx: add direct I/O alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• [PATCH v4 4/9] ext4: support STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [RFC] proc: fix create timestamp of files in proc
  • From: Muchun Song <songmuchun@xxxxxxxxxxxxx>
• [PATCH v5] Add ioctls to get/set the ext4 superblock uuid.
  • From: Jeremy Bongio <bongiojp@xxxxxxxxx>
• Re: [PATCH v5 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v5 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v5 00/13] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [RFC] proc: fix create timestamp of files in proc
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [RFC] proc: fix create timestamp of files in proc
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• Re: [RFC] proc: fix create timestamp of files in proc
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Wei Wang <wei.w.wang@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Vishal Annapurve <vannapurve@xxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: Jeremy Bongio <bongiojp@xxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• RE: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxx>
• Re: [PATCH v3 0/8] make statx() return DIO alignment information
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH v4] Add ioctls to get/set the ext4 superblock uuid.
  • From: Jeremy Bongio <bongiojp@xxxxxxxxx>
• Re: [PATCH v3] Add ioctls to get/set the ext4 superblock uuid.
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 13/14] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v3] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• RE: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: [PATCH v3] Add ioctls to get/set the ext4 superblock uuid.
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: [PATCH v7 13/14] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v3] Add ioctls to get/set the ext4 superblock uuid.
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH v3] Add ioctls to get/set the ext4 superblock uuid.
  • From: Jeremy Bongio <bongiojp@xxxxxxxxx>
• RE: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Jim Baxter <jim_baxter@xxxxxxxxxx>
• Re: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Jim Baxter <jim_baxter@xxxxxxxxxx>
• RE: [PATCH v4 0/3] initramfs: add support for xattrs in the initial ram disk
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxx>
• Re: [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [REGRESSION] recent changes to copy_file_range behavior breakage
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: recvmmsg() behaviour with MSG_PEEK flag
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: recvmmsg() behaviour with MSG_PEEK flag
  • From: Alexander Babayants <babayants.alexander@xxxxxxxxx>
• Re: [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: recvmmsg() behaviour with MSG_PEEK flag
  • From: Eric Dumazet <edumazet@xxxxxxxxxx>
• recvmmsg() behaviour with MSG_PEEK flag
  • From: Alexander Babayants <babayants.alexander@xxxxxxxxx>
• Re: [RFC] futex2: add NUMA awareness
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [RFC] futex2: add NUMA awareness
  • From: Andrey Semashev <andrey.semashev@xxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Andy Lutomirski" <luto@xxxxxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• [RFC] futex2: add NUMA awareness
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: "Gupta, Pankaj" <pankaj.gupta@xxxxxxx>
• Re: [mm-unstable v7 09/18] mm/madvise: introduce MADV_COLLAPSE sync hugepage collapse
  • From: "Zach O'Keefe" <zokeefe@xxxxxxxxxx>
• Re: [PATCH v2] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v2] Add ioctls to get/set the ext4 superblock uuid.
  • From: Jeremy Bongio <bongiojp@xxxxxxxxx>
• Re: [PATCH v4 1/2] namei: implemented RENAME_NEWER_MTIME flag for renameat2() conditional replace
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [mm-unstable v7 09/18] mm/madvise: introduce MADV_COLLAPSE sync hugepage collapse
  • From: Yang Shi <shy828301@xxxxxxxxx>
• [PATCH v4 2/2] selftests: added a new target renameat2
  • From: James Yonan <james@xxxxxxxxxxx>
• [PATCH v4 1/2] namei: implemented RENAME_NEWER_MTIME flag for renameat2() conditional replace
  • From: James Yonan <james@xxxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Xiaoyao Li <xiaoyao.li@xxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• [PATCH v7 14/14] memfd_create.2: Describe MFD_INACCESSIBLE flag
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 12/14] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 13/14] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 11/14] KVM: Register/unregister the guest private memory regions
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 10/14] KVM: Add KVM_EXIT_MEMORY_FAULT exit
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 09/14] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 07/14] KVM: Use gfn instead of hva for mmu_notifier_retry
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 08/14] KVM: Rename mmu_notifier_*
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 05/14] mm/memfd: Introduce MFD_INACCESSIBLE flag
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 06/14] KVM: Rename KVM_PRIVATE_MEM_SLOTS to KVM_INTERNAL_MEM_SLOTS
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 04/14] mm/shmem: Support memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 03/14] mm: Introduce memfile_notifier
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 02/14] selftests/memfd: Add tests for F_SEAL_AUTO_ALLOCATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 01/14] mm: Add F_SEAL_AUTO_ALLOCATE seal to memfd
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH v7 00/14] KVM: mm: fd-based approach for supporting KVM guest private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v2] Add ioctls to get/set the ext4 superblock uuid.
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [RESEND PATCH v3 1/2] namei: implemented RENAME_NEWER_MTIME flag for renameat2() conditional replace
  • From: James Yonan <james@xxxxxxxxxxx>
• [PATCH man-pages] rename.2: document new renameat2() flag RENAME_NEWER_MTIME
  • From: James Yonan <james@xxxxxxxxxxx>
• [PATCH v3 2/2] selftests: added a new target renameat2
  • From: James Yonan <james@xxxxxxxxxxx>
• [PATCH v3 1/2] RENAME_NEWER_MTIME is a new userspace-visible flag for renameat2(), and stands alongside existing flags including RENAME_NOREPLACE, RENAME_EXCHANGE, and RENAME_WHITEOUT.
  • From: James Yonan <james@xxxxxxxxxxx>
• Re: [PATCH] fanotify: refine the validation checks on non-dir inode mask
  • From: Matthew Bobrowski <repnop@xxxxxxxxxx>
• [PATCH v2] Add ioctls to get/set the ext4 superblock uuid.
  • From: Jeremy Bongio <bongiojp@xxxxxxxxx>
• Re: [PATCH v3 1/3] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 1/3] fanotify: prepare for setting event flags in ignore mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Xiaoyao Li <xiaoyao.li@xxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH v4 3/3] gen_init_cpio: add support for file metadata
  • From: Eugeniu Rosca <erosca@xxxxxxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Vishal Annapurve <vannapurve@xxxxxxxxxx>
• Re: [PATCH] namei: implemented RENAME_NEWER flag for renameat2() conditional replace
  • From: James Yonan <james@xxxxxxxxxxx>
• RE: [PATCH v4 3/3] gen_init_cpio: add support for file metadata
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxx>
• [PATCH v3 1/3] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 2/3] fanotify: cleanups for fanotify_mark() input validations
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 0/3] New fanotify API for ignoring events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v3 3/3] fanotify: introduce FAN_MARK_IGNORE
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] fanotify: refine the validation checks on non-dir inode mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] namei: implemented RENAME_NEWER flag for renameat2() conditional replace
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] namei: implemented RENAME_NEWER flag for renameat2() conditional replace
  • From: James Yonan <james@xxxxxxxxxxx>
• Re: [PATCH] fanotify: refine the validation checks on non-dir inode mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] namei: implemented RENAME_NEWER flag for renameat2() conditional replace
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH] fanotify: refine the validation checks on non-dir inode mask
  • From: Jan Kara <jack@xxxxxxx>
• [PATCH v37 32/33] LSM: Add /proc attr entry for full LSM context
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH v37 14/33] LSM: Specify which LSM to display
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH] fanotify: refine the validation checks on non-dir inode mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v2 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2 0/2] New fanotify API for ignoring events
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v2 0/2] New fanotify API for ignoring events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v3 2/8] vfs: support STATX_DIOALIGN on block devices
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v9 5/6] serial: Support for RS-485 multipoint addresses
  • From: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxxxxxx>
• [PATCH v9 0/6] Add RS485 9th bit addressing mode support to DW UART
  • From: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxxxxxx>
• [PATCH v2 0/2] New fanotify API for ignoring events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH v2 2/2] fanotify: introduce FAN_MARK_IGNORE
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 4/8] KVM: Extend the memslot to support fd-based private memory
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 4/8] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 7/8] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: "Nikunj A. Dadhania" <nikunj@xxxxxxx>
• Re: [PATCH v6 4/8] KVM: Extend the memslot to support fd-based private memory
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH v6 7/8] KVM: Enable and expose KVM_MEM_PRIVATE
  • From: Michael Roth <michael.roth@xxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [man-pages RFC PATCH] statx.2, open.2: document STATX_DIOALIGN
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [man-pages RFC PATCH] statx.2, open.2: document STATX_DIOALIGN
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [man-pages RFC PATCH] statx.2, open.2: document STATX_DIOALIGN
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v3 1/8] statx: add direct I/O alignment information
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 2/2] fanotify: introduce FAN_MARK_IGNORE
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 2/2] fanotify: introduce FAN_MARK_IGNORE
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v3] uapi: Make __{u,s}64 match {u,}int64_t in userspace
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH 1/2] rseq: Deprecate RSEQ_CS_FLAG_NO_RESTART_ON_* flags
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• [PATCH 2/2] rseq: Kill process when unknown flags are encountered in ABI structures
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Jan Kara <jack@xxxxxxx>
• Re: [RFC PATCH] f*xattr: allow O_PATH descriptors
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v3] uapi: Make __{u,s}64 match {u,}int64_t in userspace
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• RE: [PATCH v3] uapi: Make __{u,s}64 match {u,}int64_t in userspace
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: [PATCH v3] uapi: Make __{u,s}64 match {u,}int64_t in userspace
  • From: Alejandro Colomar <alx.manpages@xxxxxxxxx>
• [PATCH v3] uapi: Make __{u,s}64 match {u,}int64_t in userspace
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• Re: [LTP] [PATCH v2] uapi: Make __{u, s}64 match {u, }int64_t in userspace
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: pgprot_encrypted macro is broken
  • From: Federico Di Pierro <nierro92@xxxxxxxxx>
• [PATCH v2] uapi: Make __{u,s}64 match {u,}int64_t in userspace
  • From: Cyril Hrubis <metan@xxxxxx>
• Re: [PATCH v6 6/8] KVM: Handle page fault for private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 4/8] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• Re: [PATCH v6 4/8] KVM: Extend the memslot to support fd-based private memory
  • From: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
• [PATCH 2/2] fanotify: introduce FAN_MARK_IGNORE
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH 0/2] New fanotify API for ignoring events
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH 1/2] fanotify: prepare for setting event flags in ignore mask
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v8 5/6] serial: Support for RS-485 multipoint addresses
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: pgprot_encrypted macro is broken
  • From: Jann Horn <jannh@xxxxxxxxxx>