Linux API

• Thread Index

• Re: [PATCH v6 0/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v6 0/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v6 0/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH 00/10] mm/mremap: permit mremap() move of multiple VMAs
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH v1 00/32] Live Update Orchestrator
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• Re: [PATCH v1 00/32] Live Update Orchestrator
  • From: Jason Gunthorpe <jgg@xxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH] tree-wide: s/struct fileattr/struct file_kattr/g
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: SeongJae Park <sj@xxxxxxxxxx>
• Re: [PATCH v18 4/8] fork: Add shadow stack support to clone3()
  • From: Yury Khrustalev <yury.khrustalev@xxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH v18 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 1/8] arm64/gcs: Return a success value from gcs_alloc_thread_stack()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 3/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 2/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v18 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 2/6] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Pali Rohár <pali@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Pali Rohár <pali@xxxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Pali Rohár <pali@xxxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v6 2/6] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v6 1/6] fs: split fileattr related helpers into separate file
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
• Re: [RFC v2 00/22] Kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 2/6] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 1/6] fs: split fileattr related helpers into separate file
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v6 0/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH v4 0/3] lsm: introduce lsm_config_self_policy() and lsm_config_system_policy() syscalls
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v4 1/3] Wire up lsm_config_self_policy and lsm_config_system_policy syscalls
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v4 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v4 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [PATCH v5 1/7] selftests/futex: Add ASSERT_ macros
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v3 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v6 0/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v6 1/6] fs: split fileattr related helpers into separate file
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [RFC v2 00/22] Kernel API specification framework
  • From: Jake Edge <jake@xxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
• Re: [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Pali Rohár <pali@xxxxxxxxxx>
• [PATCH v6 6/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v6 4/6] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v6 3/6] selinux: implement inode_file_[g|s]etattr hooks
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v6 2/6] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v6 0/6] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v6 5/6] fs: prepare for extending file_get/setattr()
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v6 1/6] fs: split fileattr related helpers into separate file
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH v5 3/7] futex: Use explicit sizes for compat_exit_robust_list
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH RFT v17 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v5 1/7] selftests/futex: Add ASSERT_ macros
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [PATCH RFT v17 4/8] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH v5 7/7] selftests: futex: Expand robust list test for the new interface
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v5 5/7] futex: Remove the limit of elements for sys_set_robust_list2 lists
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v5 4/7] futex: Create set_robust_list2
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/3] Wire up lsm_config_self_policy and lsm_config_system_policy syscalls
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v5 3/7] futex: Use explicit sizes for compat_exit_robust_list
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v5 2/7] selftests/futex: Create test for robust list
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v5 1/7] selftests/futex: Add ASSERT_ macros
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v5 1/7] selftests/futex: Add ASSERT_ macros
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [PATCH v5 7/7] selftests: futex: Expand robust list test for the new interface
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 4/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 6/7] futex: Wire up set_robust_list2 syscall
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 3/7] futex: Use explicit sizes for compat_exit_robust_list
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 5/7] futex: Remove the limit of elements for sys_set_robust_list2 lists
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 2/7] selftests/futex: Create test for robust list
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 0/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v5 1/7] selftests/futex: Add ASSERT_ macros
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH v1 25/32] mm: shmem: use SHMEM_F_* flags instead of VM_* flags
  • From: Pratyush Yadav <pratyush@xxxxxxxxxx>
• [PATCH] fixup! mm: shmem: use SHMEM_F_* flags instead of VM_* flags
  • From: Pratyush Yadav <ptyadav@xxxxxxxxx>
• Re: [PATCH RFT v17 3/8] selftests: Provide helper header for shadow stack testing
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v1 29/32] docs: add documentation for memfd preservation via LUO
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v1 17/32] liveupdate: luo_sysfs: add sysfs state monitoring
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v1 21/32] liveupdate: add selftests for subsystems un/registration
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v1 03/32] kho: warn if KHO is disabled due to an error
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v1 00/32] Live Update Orchestrator
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: [PATCH v1 00/32] Live Update Orchestrator
  • From: "pasha.tatashin" <pasha.tatashin@xxxxxxxxxx>
• Re: [PATCH v1 00/32] Live Update Orchestrator
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• [RFC v1 32/32] libluo: add tests
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [RFC v1 30/32] tools: introduce libluo
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 27/32] mm: shmem: export some functions to internal.h
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 29/32] docs: add documentation for memfd preservation via LUO
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [RFC v1 31/32] libluo: introduce luoctl
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 28/32] luo: allow preserving memfd
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 26/32] mm: shmem: allow freezing inode mapping
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 25/32] mm: shmem: use SHMEM_F_* flags instead of VM_* flags
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 24/32] MAINTAINERS: add liveupdate entry
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 23/32] docs: add luo documentation
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 22/32] selftests/liveupdate: add subsystem/state tests
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 20/32] kho: move kho debugfs directory to liveupdate
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 21/32] liveupdate: add selftests for subsystems un/registration
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 19/32] liveupdate: luo_files: luo_ioctl: session-based file descriptor tracking
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 12/32] liveupdate: luo_subsystems: add subsystem registration
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 16/32] liveupdate: luo_ioctl: add ioctl interface
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 18/32] reboot: call liveupdate_reboot() before kexec
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 09/32] liveupdate: kho: move to kernel/liveupdate
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 17/32] liveupdate: luo_sysfs: add sysfs state monitoring
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 06/32] kho: drop notifiers
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 13/32] liveupdate: luo_subsystems: implement subsystem callbacks
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 15/32] liveupdate: luo_files: implement file systems callbacks
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 14/32] liveupdate: luo_files: add infrastructure for FDs
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 11/32] liveupdate: luo_core: integrate with KHO
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 10/32] liveupdate: luo_core: Live Update Orchestrator
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 08/32] kho: don't unpreserve memory during abort
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 05/32] kho: make debugfs interface optional
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 07/32] kho: add interfaces to unpreserve folios and physical memory ranges
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 03/32] kho: warn if KHO is disabled due to an error
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 02/32] kho: mm: Don't allow deferred struct page with KHO
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 04/32] kho: allow to drive kho from within kernel
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 01/32] kho: init new_physxa->phys_bits to fix lockdep
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• [PATCH v1 00/32] Live Update Orchestrator
  • From: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v3 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 22/22] tools/kapi: Add kernel API specification extraction tool
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 20/22] block: sysfs API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 18/22] binder: add detailed IOCTL API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 21/22] net/socket: add API specification for socket()
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 15/22] kernel/api: add debugfs interface for kernel API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 19/22] kernel/api: Add sysfs validation support to kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 14/22] mm/mlock: add API specification for munlockall
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 17/22] fwctl: add detailed IOCTL API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 13/22] mm/mlock: add API specification for munlock
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 16/22] kernel/api: add IOCTL specification infrastructure
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 12/22] mm/mlock: add API specification for mlockall
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 11/22] mm/mlock: add API specification for mlock2
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 09/22] exec: add API specification for execveat
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 10/22] mm/mlock: add API specification for mlock
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 08/22] exec: add API specification for execve
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 07/22] eventpoll: add API specification for epoll_pwait2
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 06/22] eventpoll: add API specification for epoll_pwait
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 04/22] eventpoll: add API specification for epoll_ctl
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 05/22] eventpoll: add API specification for epoll_wait
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 03/22] eventpoll: add API specification for epoll_create
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 02/22] eventpoll: add API specification for epoll_create1
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 01/22] kernel/api: introduce kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC v2 00/22] Kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• [PATCH v3 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v3 1/3] Wire up lsm_config_self_policy and lsm_config_system_policy syscalls
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v3 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v3 0/3] lsm: introduce lsm_config_self_policy() and lsm_config_system_policy() syscalls
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
• Re: [PATCH v2 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH v2 3/3] AppArmor: add support for lsm_config_self_policy and lsm_config_system_policy
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v2 2/3] lsm: introduce security_lsm_config_*_policy hooks
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v2 1/3] Wire up lsm_config_self_policy and lsm_config_system_policy syscalls
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH v2 0/3] lsm: introduce lsm_config_self_policy() and lsm_config_system_policy() syscalls
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RESEND v4 0/7] futex: Create set_robust_list2
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH RESEND v4 0/7] futex: Create set_robust_list2
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [PATCH RESEND v4 0/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [PATCH RESEND v4 0/7] futex: Create set_robust_list2
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [RFC 08/19] exec: add API specification for execve
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH RESEND v4 7/7] selftests: futex: Expand robust list test for the new interface
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 5/7] futex: Wire up set_robust_list2 syscall
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 3/7] futex: Use explicit sizes for compat_exit_robust_list
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 4/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 2/7] selftests/futex: Create test for robust list
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 6/7] futex: Remove the limit of elements for sys_set_robust_list2 lists
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 0/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH RESEND v4 1/7] selftests/futex: Add ASSERT_ macros
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: [RFC 00/19] Kernel API Specification Framework
  • From: David Laight <david.laight.linux@xxxxxxxxx>
• Re: [RFC 08/19] exec: add API specification for execve
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC 08/19] exec: add API specification for execve
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [RFC 08/19] exec: add API specification for execve
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [RFC 18/19] binder: add detailed IOCTL API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 19/19] tools/kapi: Add kernel API specification extraction tool
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 16/19] kernel/api: add IOCTL specification infrastructure
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 17/19] fwctl: add detailed IOCTL API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 15/19] kernel/api: add debugfs interface for kernel API specifications
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 14/19] mm/mlock: add API specification for munlockall
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 13/19] mm/mlock: add API specification for munlock
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 12/19] mm/mlock: add API specification for mlockall
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 11/19] mm/mlock: add API specification for mlock2
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 09/19] exec: add API specification for execveat
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 10/19] mm/mlock: add API specification for mlock
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 08/19] exec: add API specification for execve
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 07/19] eventpoll: add API specification for epoll_pwait2
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 06/19] eventpoll: add API specification for epoll_pwait
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 03/19] eventpoll: add API specification for epoll_create
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 04/19] eventpoll: add API specification for epoll_ctl
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 05/19] eventpoll: add API specification for epoll_wait
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 02/19] eventpoll: add API specification for epoll_create1
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 01/19] kernel/api: introduce kernel API specification framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [RFC 00/19] Kernel API Specification Framework
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH 07/10] fs: introduce FALLOC_FL_WRITE_ZEROES to fallocate
  • From: Zhang Yi <yi.zhang@xxxxxxxxxxxxxxx>
• Re: [PATCH] man/man2/memfd_secret.2: Correct the flags
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH 07/10] fs: introduce FALLOC_FL_WRITE_ZEROES to fallocate
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [PATCH RFT v17 4/8] fork: Add shadow stack support to clone3()
  • From: Yury Khrustalev <yury.khrustalev@xxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH net-next v3 2/6] tcp: copy write-data from listen socket to accept child socket
  • From: Eric Dumazet <edumazet@xxxxxxxxxx>
• [PATCH net-next v3 6/6] tcp: fastopen: extend retransmit-queue trimming to handle linear sk_buff
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v3 4/6] tcp: transmit any pending data on receipt of 3rd-ack
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v3 2/6] tcp: copy write-data from listen socket to accept child socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v3 3/6] tcp: fastopen: add write-data to fastopen synack packet
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v3 5/6] tcp: fastopen: retransmit data when only the SYN of a synack-with-data is acked
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v3 1/6] tcp: support writing to a socket in listening state
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v3 0/6] tcp: support preloading data on a listening socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH RFT v17 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 3/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 2/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v17 1/8] arm64/gcs: Return a success value from gcs_alloc_thread_stack()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: Extending clone_args for clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Extending clone_args for clone3()
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH 5.4 193/204] pidfd: check pid has attached task in fdinfo
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Extending clone_args for clone3()
  • From: Yury Khrustalev <yury.khrustalev@xxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: "Liam R. Howlett" <Liam.Howlett@xxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Shakeel Butt <shakeel.butt@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Usama Arif <usamaarif642@xxxxxxxxx>
• Re: [DISCUSSION] proposed mctl() API
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [DISCUSSION] proposed mctl() API
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [RFC v2 00/16] Live Update Orchestrator
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: [PATCH v5 3/7] selinux: implement inode_file_[g|s]etattr hooks
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/5] add process_madvise() flags to modify behaviour
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• Re: [PATCH v3 0/7] prctl: introduce PR_SET/GET_THP_POLICY
  • From: Mike Rapoport <rppt@xxxxxxxxxx>
• Re: [PATCH v4 4/7] futex: Create set_robust_list2
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH net-next v2 1/6] tcp: support writing to a socket in listening state
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v4 5/7] futex: Wire up set_robust_list2 syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v4 4/7] futex: Create set_robust_list2
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH v4 3/7] futex: Use explicit sizes for compat_exit_robust_list
  • From: kernel test robot <lkp@xxxxxxxxx>
• [PATCH net-next v2 2/6] tcp: copy write-data from listen socket to accept child socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v2 0/6] tcp: support preloading data on a listening socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v2 5/6] tcp: fastopen: retransmit data when only the SYN of a synack-with-data is acked
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v2 3/6] tcp: fastopen: add write-data to fastopen synack packet
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v2 4/6] tcp: transmit any pending data on receipt of 3rd-ack
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v2 6/6] tcp: fastopen: extend retransmit-queue trimming to handle linear sk_buff
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH net-next v2 1/6] tcp: support writing to a socket in listening state
  • From: Jeremy Harris <jgh@xxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Pali Rohár <pali@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Steffen Nurpmeso <steffen@xxxxxxxxxx>
• [PATCH v4 7/7] selftests: futex: Expand robust list test for the new interface
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 6/7] futex: Remove the limit of elements for sys_set_robust_list2 lists
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 5/7] futex: Wire up set_robust_list2 syscall
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 4/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 3/7] futex: Use explicit sizes for compat_exit_robust_list
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 2/7] selftests/futex: Create test for robust list
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 0/7] futex: Create set_robust_list2
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• [PATCH v4 1/7] selftests/futex: Add ASSERT_ macros
  • From: André Almeida <andrealmeid@xxxxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Steffen Nurpmeso <steffen@xxxxxxxxxx>
• Extending clone_args for clone3()
  • From: Yury Khrustalev <yury.khrustalev@xxxxxxx>
• Re: mlock ulimits for SHM_HUGETLB
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: mlock ulimits for SHM_HUGETLB
  • From: Bharat Agrawal <bharat.agrawal@xxxxxxxxx>
• Re: mlock ulimits for SHM_HUGETLB
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: mlock ulimits for SHM_HUGETLB
  • From: Bharat Agrawal <bharat.agrawal@xxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: mlock ulimits for SHM_HUGETLB
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: mlock ulimits for SHM_HUGETLB
  • From: Bharat Agrawal <bharat.agrawal@xxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH 2/6] tcp: copy write-data from listen socket to accept child socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• Re: [PATCH 0/6] tcp: support preloading data on a listening socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/6] tcp: support preloading data on a listening socket
  • From: Neal Cardwell <ncardwell@xxxxxxxxxx>
• Re: [PATCH 2/6] tcp: copy write-data from listen socket to accept child socket
  • From: Eric Dumazet <edumazet@xxxxxxxxxx>
• Re: [PATCH 0/6] tcp: support preloading data on a listening socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 3/6] tcp: fastopen: add write-data to fastopen synack packet
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 4/6] tcp: transmit any pending data on receipt of 3rd-ack
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 2/6] tcp: copy write-data from listen socket to accept child socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 6/6] tcp: fastopen: extend retransmit-queue trimming to handle linear sk_buff
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 1/6] tcp: support writing to a socket in listening state
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 5/6] tcp: fastopen: retransmit data when only the SYN of a synack-with-data is acked
  • From: Jeremy Harris <jgh@xxxxxxxx>
• [PATCH 0/6] tcp: support preloading data on a listening socket
  • From: Jeremy Harris <jgh@xxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Vincent Lefevre <vincent@xxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Vincent Lefevre <vincent@xxxxxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Rich Felker <dalias@xxxxxxxx>
• [RFC v1] man/man2/close.2: CAVEATS: Document divergence from POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: close(2) with EINTR has been changed by POSIX.1-2024
  • From: Jan Kara <jack@xxxxxxx>
• close(2) with EINTR has been changed by POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• [PATCH v5 7/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 6/7] fs: prepare for extending file_get/setattr()
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 5/7] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 3/7] selinux: implement inode_file_[g|s]etattr hooks
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 4/7] fs: split fileattr/fsxattr converters into helpers
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 1/7] fs: split fileattr related helpers into separate file
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v5 5/7] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 1/7] fs: split fileattr related helpers into separate file
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 5/7] fs: make vfs_fileattr_[get|set] return -EOPNOSUPP
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 3/7] selinux: implement inode_file_[g|s]etattr hooks
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 4/7] fs: split fileattr/fsxattr converters into helpers
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 1/7] fs: split fileattr related helpers into separate file
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 2/7] lsm: introduce new hooks for setting/getting inode fsxattr
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v5 0/7] fs: introduce file_getattr and file_setattr syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: The "make headers" requirement, revisited: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: The "make headers" requirement, revisited: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Song Liu <song@xxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: The "make headers" requirement, revisited: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [PATCH v12 17/17] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: kernel test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Song Liu <song@xxxxxxxxxx>
• Re: [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Song Liu <song@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• [PATCH 3/3] AppArmor: add support for lsm_manage_policy
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH 0/3] lsm: introduce lsm_manage_policy() syscall
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH 2/3] lsm: introduce security_lsm_manage_policy hook
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• [PATCH 1/3] Wire up the lsm_manage_policy syscall
  • From: Maxime Bélair <maxime.belair@xxxxxxxxxxxxx>
• Re: [PATCH v12 02/17] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• [PATCH v12 16/17] xfs: update atomic write limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 15/17] xfs: add xfs_calc_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 14/17] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 13/17] xfs: commit CoW-based atomic writes atomically
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 17/17] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 12/17] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 09/17] xfs: refactor xfs_reflink_end_cow_extent()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 07/17] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 11/17] xfs: add xfs_atomic_write_cow_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 05/17] xfs: add helpers to compute log item overhead
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 06/17] xfs: add helpers to compute transaction reservation for finishing intent items
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 10/17] xfs: refine atomic write size check in xfs_file_write_iter()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 08/17] xfs: allow block allocator to take an alignment hint
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 01/17] fs: add atomic write unit max opt to statx
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 04/17] xfs: separate out setting buftarg atomic writes limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 02/17] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 03/17] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v12 00/17] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v1 bpf-next 4/5] bpf: Add kfunc to scrub SCM_RIGHTS at security_unix_may_send().
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v10 13/15] xfs: add xfs_calc_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH v11 06/16] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 15/16] xfs: update atomic write limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 13/16] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 05/16] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 07/16] xfs: allow block allocator to take an alignment hint
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 09/16] xfs: refine atomic write size check in xfs_file_write_iter()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 14/16] xfs: add xfs_calc_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 10/16] xfs: add xfs_atomic_write_cow_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 11/16] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 16/16] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 12/16] xfs: commit CoW-based atomic writes atomically
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 04/16] xfs: add helpers to compute transaction reservation for finishing intent items
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 08/16] xfs: refactor xfs_reflink_end_cow_extent()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 03/16] xfs: add helpers to compute log item overhead
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 01/16] fs: add atomic write unit max opt to statx
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 00/16] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v11 02/16] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10.1 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH v10.1 1.1/15] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH 16/15] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH 17/15] xfs: move buftarg atomic write geometry config to setsize_buftarg
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 16/15] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] man/man2/clone.2: Document CLONE_NEWPID and CLONE_NEWUSER flag
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 17/15] xfs: move buftarg atomic write geometry config to setsize_buftarg
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH 16/15] xfs: only call xfs_setsize_buftarg once per buffer target
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Sean Christopherson <seanjc@xxxxxxxxxx>
• [PATCH v10 07/15] xfs: refactor xfs_reflink_end_cow_extent()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 11/15] xfs: commit CoW-based atomic writes atomically
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 14/15] xfs: update atomic write limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 06/15] xfs: allow block allocator to take an alignment hint
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 09/15] xfs: add xfs_atomic_write_cow_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 03/15] xfs: add helpers to compute transaction reservation for finishing intent items
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 08/15] xfs: refine atomic write size check in xfs_file_write_iter()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 13/15] xfs: add xfs_calc_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 12/15] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 04/15] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 02/15] xfs: add helpers to compute log item overhead
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 01/15] fs: add atomic write unit max opt to statx
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v10 00/15] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 00/15] large atomic writes for xfs
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v3 3/3] selftests: pidfd: add tests for PIDFD_SELF_*
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v9 00/15] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v9 00/15] large atomic writes for xfs
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 00/15] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9.1 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v9 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• [PATCH v9 00/15] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 02/15] xfs: add helpers to compute log item overhead
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 09/15] xfs: add xfs_atomic_write_cow_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 06/15] xfs: allow block allocator to take an alignment hint
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 07/15] xfs: refactor xfs_reflink_end_cow_extent()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 08/15] xfs: refine atomic write size check in xfs_file_write_iter()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 04/15] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomic_write()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 14/15] xfs: update atomic write limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 12/15] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 11/15] xfs: commit CoW-based atomic writes atomically
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 03/15] xfs: add helpers to compute transaction reservation for finishing intent items
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v9 01/15] fs: add atomic write unit max opt to statx
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH] fs: push retrieval of fileattr down to filesystems
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: newlines in filenames; POSIX.1-2024
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Andrey Albershteyn <aalbersh@xxxxxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: newlines in filenames; POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: newlines in filenames; POSIX.1-2024
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v8 11/15] xfs: commit CoW-based atomic writes atomically
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v8 11/15] xfs: commit CoW-based atomic writes atomically
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 11/15] xfs: commit CoW-based atomic writes atomically
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v8 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v8 11/15] xfs: commit CoW-based atomic writes atomically
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v8 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 12/15] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v8 14/15] xfs: update atomic write limits
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 12/15] xfs: add xfs_file_dio_write_atomic()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 11/15] xfs: commit CoW-based atomic writes atomically
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v8 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 09/15] xfs: add xfs_atomic_write_cow_iomap_begin()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: newlines in filenames; POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: newlines in filenames; POSIX.1-2024
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v4 3/3] fs: introduce getfsxattrat and setfsxattrat syscalls
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH v8 12/15] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 08/15] xfs: refine atomic write size check in xfs_file_write_iter()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 10/15] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 15/15] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 13/15] xfs: add xfs_compute_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 14/15] xfs: update atomic write limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 11/15] xfs: commit CoW-based atomic writes atomically
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 09/15] xfs: add xfs_atomic_write_cow_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 06/15] xfs: allow block allocator to take an alignment hint
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 07/15] xfs: refactor xfs_reflink_end_cow_extent()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 04/15] xfs: rename xfs_inode_can_atomicwrite() -> xfs_inode_can_hw_atomicwrite()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 05/15] xfs: ignore HW which cannot atomic write a single block
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 03/15] xfs: add helpers to compute transaction reservation for finishing intent items
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 02/15] xfs: add helpers to compute log item overhead
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 01/15] fs: add atomic write unit max opt to statx
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v8 00/15] large atomic writes for xfs
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH 3/4] tools/selftests: expand all guard region tests to file-backed
  • From: Ryan Roberts <ryan.roberts@xxxxxxx>
• Re: [PATCH 3/4] tools/selftests: expand all guard region tests to file-backed
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 3/4] tools/selftests: expand all guard region tests to file-backed
  • From: Ryan Roberts <ryan.roberts@xxxxxxx>
• Re: [PATCH 3/4] tools/selftests: expand all guard region tests to file-backed
  • From: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx>
• Re: [PATCH 3/4] tools/selftests: expand all guard region tests to file-backed
  • From: Ryan Roberts <ryan.roberts@xxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: Kairui Song <ryncsn@xxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v7 11/14] xfs: add xfs_file_dio_write_atomic()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• [PATCH] man/man2/clone.2: Document CLONE_NEWPID and CLONE_NEWUSER flag
  • From: devhoodit <devhoodit@xxxxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: Kairui Song <ryncsn@xxxxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: Kairui Song <ryncsn@xxxxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v3 13/20] mm: Copy-on-Write (COW) reuse support for PTE-mapped THP
  • From: Kairui Song <ryncsn@xxxxxxxxx>
• newlines in filenames; POSIX.1-2024
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v7.1 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7.1 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH RFT v16 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 3/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 2/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 1/8] arm64/gcs: Return a success value from gcs_alloc_thread_stack()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v16 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v7.1 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 09/14] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v7 09/14] xfs: add large atomic writes checks in xfs_direct_write_iomap_begin()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 12/14] xfs: add xfs_compute_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 12/14] xfs: add xfs_compute_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [PATCH v7 13/14] xfs: update atomic write limits
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 12/14] xfs: add xfs_compute_atomic_write_unit_max()
  • From: "Darrick J. Wong" <djwong@xxxxxxxxxx>
• Re: [PATCH v7 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH RFT v15 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v7 14/14] xfs: allow sysadmins to specify a maximum atomic write limit at mount time
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v7 13/14] xfs: update atomic write limits
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• [PATCH v7 12/14] xfs: add xfs_compute_atomic_write_unit_max()
  • From: John Garry <john.g.garry@xxxxxxxxxx>