Linux API

• Thread Index

• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v2 1/2] statx: update headers to include newer statx fields
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• [PATCH xfstests v2 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v2 1/2] statx: update headers to include newer statx fields
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RFC 1/8] uaccess: add copy_struct_to_user helper
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH RESEND v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH RESEND v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Jan Kara <jack@xxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [PATCH RESEND v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Jan Kara <jack@xxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH RFC 1/8] uaccess: add copy_struct_to_user helper
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• [PATCH RFC 8/8] selftests: clone3: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 7/8] selftests: openat2: add CHECK_FIELDS selftests
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 6/8] selftests: openat2: add 0xFF poisoned data after misaligned struct
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 5/8] clone3: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 4/8] openat2: add CHECK_FIELDS flag to usize argument
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 3/8] openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 2/8] sched_getattr: port to copy_struct_to_user
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 1/8] uaccess: add copy_struct_to_user helper
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC 0/8] extensible syscalls: CHECK_FIELDS to allow for easier feature detection
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH xfstests v1 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: "H.J. Lu" <hjl.tools@xxxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [musl] AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Szabolcs Nagy <nsz@xxxxxxxxxx>
• Re: [PATCH xfstests v1 2/2] open_by_handle: add tests for u64 mount ID
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• AT_MINSIGSTKSZ mismatched interpretation kernel vs libc
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: [PATCH RFC v2 0/4] mm: Introduce MAP_BELOW_HINT
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: [PATCH RFC v2 0/4] mm: Introduce MAP_BELOW_HINT
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH xfstests v1 2/2] open_by_handle: add tests for u64 mount ID
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH xfstests v1 1/2] statx: update headers to include newer statx fields
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RESEND v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RESEND v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RESEND v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: Recommended version handshake for FUSE clients
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Recommended version handshake for FUSE clients
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] random: vDSO getrandom() must reject invalid flag
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH] random: vDSO getrandom() must reject invalid flag
  • From: Yann Droneaud <yann@xxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Yangyu Chen <cyy@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Yangyu Chen <cyy@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Yangyu Chen <cyy@xxxxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• [PATCH RFT v10 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 3/8] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 2/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 1/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v10 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v9 2/8] selftests: Provide helper header for shadow stack testing
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Manpower Recruitment For Canada™
  • From: TFWP PROGRAM <admin@tandagat.online>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Willy Tarreau <w@xxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Willy Tarreau <w@xxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: It is correct to introduce new sys calls to stable versions?
  • From: Cyril Hrubis <chrubis@xxxxxxx>
• It is correct to introduce new sys calls to stable versions?
  • From: Miao Wang <shankerwangmiao@xxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Levi Zim <rsworktech@xxxxxxxxxxx>
• [PATCH RFT v9 8/8] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 7/8] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 6/8] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 5/8] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 4/8] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 3/8] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 2/8] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 1/8] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v9 0/8] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Charlie Jenkins <charlie@xxxxxxxxxxxx>
• Re: [PATCH v3 1/3] riscv: mm: Use hint address in mmap if available
  • From: Levi Zim <rsworktech@xxxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH v5 00/28] NT synchronization primitive driver
  • From: Elizabeth Figura <zfigura@xxxxxxxxxxxxxxx>
• Manpower Recruitment For Canada™
  • From: TFWP-PROGRAM <administrator@toneromala.space>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Kees Cook <kees@xxxxxxxxxx>
• [PATCH RFT v8 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 8/9] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 7/9] selftests/clone3: Explicitly handle child exits due to signals
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 6/9] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 5/9] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 2/9] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v8 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Pedro Falcato <pedro.falcato@xxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: "Nicholas Piggin" <npiggin@xxxxxxxxx>
• Re: [PATCH RFT v7 0/9] fork: Support shadow stacks in clone3()
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Pedro Falcato <pedro.falcato@xxxxxxxxx>
• Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per_sec -4.4% regression
  • From: kernel test robot <oliver.sang@xxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Rudi Heitbaum <rudi@xxxxxxxxxxxx>
• Re: [GIT PULL] asm-generic: fixes for 6.11
  • From: pr-tracker-bot@xxxxxxxxxx
• [GIT PULL] asm-generic: fixes for 6.11
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH RFC v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re:[PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH RFC v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH RFC v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Zijian Zhang <zijianzhang@xxxxxxxxxxxxx>
• Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Zijian Zhang <zijianzhang@xxxxxxxxxxxxx>
• Re: [PATCH RFC v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Josef Bacik <josef@xxxxxxxxxxxxxx>
• [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
  • From: Arnd Bergmann <arnd@xxxxxxxxxx>
• Re: syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• [PATCH v5] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH RFC v3 2/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 1/2] uapi: explain how per-syscall AT_* flags should be allocated
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH RFC v3 0/2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH v3] usb: gadget: f_fs: add capability for dfu run-time descriptor
  • From: Chris Wulff <crwulff@xxxxxxxxx>
• Re: [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: Willem de Bruijn <willemdebruijn.kernel@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• [PATCH v4] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• [PATCH RFT v7 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 8/9] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 7/9] selftests/clone3: Explicitly handle child exits due to signals
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 6/9] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 5/9] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 2/9] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v7 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v3] usb: gadget: f_fs: add capability for dfu run-time descriptor
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re:[PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: "潘少" <i@xxxxxxxxxx>
• Re: [PATCH 7/8] fs: add an ioctl to get the mnt ns id from nsfs
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH] nsfs: fix ioctl declaration
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH net-next v8 3/3] selftests: add MSG_ZEROCOPY msg_control notification test
  • From: zijianzhang@xxxxxxxxxxxxx
• [PATCH net-next v8 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control
  • From: zijianzhang@xxxxxxxxxxxxx
• [PATCH net-next v8 1/3] sock: support copying cmsgs to the user space in sendmsg
  • From: zijianzhang@xxxxxxxxxxxxx
• [PATCH net-next v8 0/3] net: A lightweight zero-copy notification mechanism for MSG_ZEROCOPY
  • From: zijianzhang@xxxxxxxxxxxxx
• Re: [PATCH 7/8] fs: add an ioctl to get the mnt ns id from nsfs
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Mateusz Guzik <mjguzik@xxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing if two open descriptors refer to the same inode
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Testing if two open descriptors refer to the same inode
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [PATCH v2] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Andy Pan via B4 Relay <devnull+i.andypan.me@xxxxxxxxxx>
• Re: [PATCH] epoll.7: clarify the event distribution under edge-triggered mode
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• Re: [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v2] vfs: add RWF_NOAPPEND flag for pwritev2
  • From: John Garry <john.g.garry@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: "Jarkko Sakkinen" <jarkko@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: enh <enh@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Boris Lukashev <rageltman@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: mprotect PROT_SIGNAL
  • From: "Soni \"They/Them\" L." <fakedme@xxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Roberto Sassu <roberto.sassu@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: mprotect PROT_SIGNAL
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• [no subject]
  • From: Unknown
• [question] about NFS4 ACLs
  • From: Mathias Dufresne <mathias.dufresne@xxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH RFT v6 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Thiago Jung Bauermann <thiago.bauermann@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• [PATCH 2/2] selftests/bpf: Change uretprobe syscall number in uprobe_syscall test
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCH 1/2] uprobe: Change uretprobe syscall scope and number
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCH 0/2] uprobe: Fix uretprobe syscall wiring
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCH v23 4/4] selftests/vDSO: add tests for vgetrandom
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 3/4] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 2/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v23 0/4] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Yu Zhao <yuzhao@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH] binfmt_elf: Fail execution of shared objects with ELIBEXEC (was: Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2))
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 5/5] samples/should-exec: Add set-should-exec
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• mprotect PROT_SIGNAL
  • From: "Soni \"They/Them\" L." <fakedme@xxxxxxxxx>
• [PATCH v22 4/4] selftests/vDSO: add tests for vgetrandom
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 3/4] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 2/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 1/4] mm: add MAP_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v22 0/4] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Steve Dower <steve.dower@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [RFC PATCH v19 5/5] samples/should-exec: Add set-should-exec
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH] binfmt_elf: Fail execution of shared objects with ELIBEXEC
  • From: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
• Re: [PATCH] binfmt_elf: Fail execution of shared objects with ELIBEXEC
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• [PATCH] binfmt_elf: Fail execution of shared objects with ELIBEXEC (was: Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2))
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Jeff Xu <jeffxu@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: David Hildenbrand <david@xxxxxxxxxx>
• [PATCH v21 4/4] selftests/vDSO: add tests for vgetrandom
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v21 3/4] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v21 2/4] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v21 0/4] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: "Jarkko Sakkinen" <jarkko@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v3] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Andy Lutomirski <luto@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: "Jarkko Sakkinen" <jarkko@xxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Kees Cook <kees@xxxxxxxxxx>
• [RFC PATCH v19 3/5] selftests/exec: Add tests for AT_CHECK and related securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [RFC PATCH v19 4/5] selftests/landlock: Add tests for execveat + AT_CHECK
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [RFC PATCH v19 5/5] samples/should-exec: Add set-should-exec
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [RFC PATCH v19 1/5] exec: Add a new AT_CHECK flag to execveat(2)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [RFC PATCH v19 2/5] security: Add new SHOULD_EXEC_CHECK and SHOULD_EXEC_RESTRICT securebits
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• [RFC PATCH v19 0/5] Script execution control (was O_MAYEXEC)
  • From: Mickaël Salaün <mic@xxxxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Beau Belgrave <beaub@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v20 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v20 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Arnd Bergmann" <arnd@xxxxxxxx>
• [PATCH v20 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v20 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v20 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v20 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v20 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v20 0/5] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v19 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>
• Re: [PATCH v19 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v19 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v19 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v19 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v19 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v19 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v19 0/5] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH] uapi: change TRACE_MMAP_IOCTL_GET_READER to avoid collision with TCGETS
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v23 3/5] tracing: Allow user-space mapping of the ring-buffer
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxx>
• Re: [PATCH] syscalls: fix sys_fanotify_mark prototype
  • From: Helge Deller <deller@xxxxxx>
• [PATCH] syscalls: fix sys_fanotify_mark prototype
  • From: Arnd Bergmann <arnd@xxxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v18 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v18 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [PATCH v3] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: Devin Bayer <dev@xxxxxxxxx>
• Re: [PATCH RFT v6 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: Devin Bayer <dev@xxxxxxxxx>
• Re: [PATCH v2] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxxxxxx>
• Re: [PATCH v2] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: "Luke Jones" <luke@xxxxxxxxxx>
• Re: [PATCH RFC] LSM, net: Add SO_PEERCONTEXT for peer LSM data
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v2] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxxxxxx>
• [PATCH RFT v6 9/9] selftests/clone3: Test shadow stack support
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 8/9] selftests/clone3: Allow tests to flag if -E2BIG is a valid error code
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 7/9] selftests/clone3: Explicitly handle child exits due to signals
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 6/9] selftests/clone3: Factor more of main loop into test_clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 5/9] selftests/clone3: Remove redundant flushes of output streams
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 4/9] fork: Add shadow stack support to clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 3/9] mm: Introduce ARCH_HAS_USER_SHADOW_STACK
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 2/9] selftests: Provide helper header for shadow stack testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 1/9] Documentation: userspace-api: Add shadow stack API documentation
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH RFT v6 0/9] fork: Support shadow stacks in clone3()
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH RFC] LSM, net: Add SO_PEERCONTEXT for peer LSM data
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH RFC] LSM, net: Add SO_PEERCONTEXT for peer LSM data
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH RFC] LSM, net: Add SO_PEERCONTEXT for peer LSM data
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: "Luke Jones" <luke@xxxxxxxxxx>
• Re: [PATCH 1/2] platform/x86: asus-wmi: support camera disable LED
  • From: "Luke Jones" <luke@xxxxxxxxxx>
• [PATCH v2] platform/x86: asus-wmi: support the disable camera LED on F10 of Zenbook 2023
  • From: Devin Bayer <dev@xxxxxxxxx>
• Re: [PATCH 2/2] platform/x86: asus-wmi: support newer fan_boost_mode dev_id
  • From: Devin Bayer <dev@xxxxxxxxx>
• Re: [PATCH 1/2] platform/x86: asus-wmi: support camera disable LED
  • From: Devin Bayer <dev@xxxxxxxxx>
• Re: [PATCH 1/2] platform/x86: asus-wmi: support camera disable LED
  • From: "Luke Jones" <luke@xxxxxxxxxx>
• Re: [PATCH 2/2] platform/x86: asus-wmi: support newer fan_boost_mode dev_id
  • From: "Luke Jones" <luke@xxxxxxxxxx>
• Re: [PATCH RFC] LSM, net: Add SO_PEERCONTEXT for peer LSM data
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCHv8 bpf-next 3/9] uprobe: Add uretprobe syscall to speed up return probe
  • From: Oleg Nesterov <oleg@xxxxxxxxxx>
• Re: [PATCHv8 bpf-next 3/9] uprobe: Add uretprobe syscall to speed up return probe
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH 1/2] platform/x86: asus-wmi: support camera disable LED
  • From: Devin Bayer <dev@xxxxxxxxx>
• [PATCH 2/2] platform/x86: asus-wmi: support newer fan_boost_mode dev_id
  • From: Devin Bayer <dev@xxxxxxxxx>
• [PATCH 0/2] platform/x86: asus-wmi: support a couple Zenbook 2023 features
  • From: Devin Bayer <dev@xxxxxxxxx>
• Re: [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• [PATCH v18 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v18 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v18 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v18 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v18 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v18 0/5] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• RE: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v1 11/14] futex: Implement FUTEX2_NUMA
  • From: "Christoph Lameter (Ampere)" <cl@xxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v17 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v17 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH v17 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCHv8 bpf-next 3/9] uprobe: Add uretprobe syscall to speed up return probe
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• Re: [PATCHv8 bpf-next 3/9] uprobe: Add uretprobe syscall to speed up return probe
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• [PATCH v17 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v17 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v17 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v17 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v17 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v17 0/5] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCHv8 bpf-next 3/9] uprobe: Add uretprobe syscall to speed up return probe
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: enh <enh@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: enh <enh@xxxxxxxxxx>
• Re: [PATCH v1 11/14] futex: Implement FUTEX2_NUMA
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v1 11/14] futex: Implement FUTEX2_NUMA
  • From: "Christoph Lameter (Ampere)" <cl@xxxxxxxxx>
• Re: [PATCH v1 11/14] futex: Implement FUTEX2_NUMA
  • From: "Christoph Lameter (Ampere)" <cl@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH] uapi/asm/termbits: Use the U integer suffix for bit fields
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: [PATCH] uapi/asm/termbits: Use the U integer suffix for bit fields
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] uapi/asm/termbits: Use the U integer suffix for bit fields
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH] uapi/asm/termbits: Use the U integer suffix for bit fields
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] uapi/asm/termbits: Use the U integer suffix for bit fields
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: termios constants should be unsigned
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• termios constants should be unsigned
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCH v1 0/2] uapi/linux/prctl: Use the L and UL integer suffixes for certain constants
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCHv8 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: [PATCHv8 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Alejandro Colomar <alx@xxxxxxxxxx>
• Re: [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCHv7 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• [PATCHv8 9/9] man2: Add uretprobe syscall page
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 8/9] selftests/bpf: Add uretprobe shadow stack test
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 7/9] selftests/bpf: Add uretprobe syscall call from user space test
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 6/9] selftests/bpf: Add uretprobe syscall test for regs changes
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 5/9] selftests/bpf: Add uretprobe syscall test for regs integrity
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 4/9] selftests/x86: Add return uprobe shadow stack test
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 3/9] uprobe: Add uretprobe syscall to speed up return probe
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 2/9] uprobe: Wire up uretprobe system call
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 1/9] x86/shstk: Make return uprobe work with shadow stack
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• [PATCHv8 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Jiri Olsa <jolsa@xxxxxxxxxx>
• Re: [PATCHv7 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: [PATCHv7 bpf-next 2/9] uprobe: Wire up uretprobe system call
  • From: Jiri Olsa <olsajiri@xxxxxxxxx>
• Re: [PATCHv7 bpf-next 2/9] uprobe: Wire up uretprobe system call
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCHv7 bpf-next 8/9] selftests/bpf: Add uretprobe shadow stack test
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCHv7 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>
• Re: [PATCH v5 00/28] NT synchronization primitive driver
  • From: Elizabeth Figura <zfigura@xxxxxxxxxxxxxxx>
• Re: [PATCHv7 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v16 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCHv7 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: [PATCH v16 2/5] random: add vgetrandom_alloc() syscall
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Header conflicts with shmget() and SHM_HUGE_2MB
  • From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
• Header conflicts with shmget() and SHM_HUGE_2MB
  • From: Carlos Llamas <cmllamas@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH v16 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Aleksa Sarai <cyphar@xxxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCHv7 bpf-next 0/9] uprobe: uretprobe speed up
  • From: Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Jann Horn <jannh@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v16 2/5] random: add vgetrandom_alloc() syscall
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH v16 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCHv6 bpf-next 1/9] x86/shstk: Make return uprobe work with shadow stack
  • From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
• Re: [PATCH v5 1/3] VT: Use macros to define ioctls
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5 1/3] VT: Use macros to define ioctls
  • From: "Arnd Bergmann" <arnd@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: [PATCH v5 1/3] VT: Use macros to define ioctls
  • From: Jiri Slaby <jirislaby@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: "hch@xxxxxxxxxxxxx" <hch@xxxxxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: Frank van der Linden <fvdl@xxxxxxxxxx>
• Re: [PATCH v16 0/5] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v16 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH v16 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH v16 5/5] x86: vdso: Wire up getrandom() vDSO implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v16 4/5] random: introduce generic vDSO getrandom() implementation
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v16 3/5] arch: allocate vgetrandom_alloc() syscall number
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v16 2/5] random: add vgetrandom_alloc() syscall
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v16 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• [PATCH v16 0/5] implement getrandom() in vDSO
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH RFC v2] fhandle: expose u64 mount id to name_to_handle_at(2)
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• [PATCH v1 2/2] uapi/linux/prctl: Use the UL integer suffix for bit fields of width long
  • From: Alejandro Colomar <alx@xxxxxxxxxx>