kernel-hardening mailing list - 2019/06

Follow @Openwall on Twitter for new release announcements and other news

[<prev month] [next month>] [year] [list]

kernel-hardening mailing list - 2019/06

Mon	Tue	Wed	Thu	Fri	Sat	Sun
					¹ 10	² 3
³ 7	⁴ 10	⁵ 5	⁶	⁷ 12	⁸ 4	⁹
¹⁰ 17	¹¹ 6	¹² 19	¹³ 21	¹⁴ 9	¹⁵ 2	¹⁶ 2
¹⁷ 17	¹⁸ 15	¹⁹ 15	²⁰ 2	²¹ 14	²²	²³
²⁴ 6	²⁵ 27	²⁶ 23	²⁷ 43	²⁸ 8	²⁹ 4	³⁰

Messages by day:

June 1 (10 messages)

Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time (Andrew Morton <akpm@...ux-foundation.org>)
[PATCH AUTOSEL 5.1 037/186] gcc-plugins: arm_ssp_per_task_plugin: Fix for older GCC < 6 (Sasha Levin <sashal@...nel.org>)
[PATCH AUTOSEL 5.0 034/173] gcc-plugins: arm_ssp_per_task_plugin: Fix for older GCC < 6 (Sasha Levin <sashal@...nel.org>)
[RFC 0/6] Harden list_for_each_entry_rcu() and family ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
[RFC 1/6] rcu: Add support for consolidated-RCU reader checking ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
[RFC 2/6] ipv4: add lockdep condition to fix for_each_entry ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
[RFC 3/6] driver/core: Convert to use built-in RCU list checking ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
[RFC 4/6] workqueue: Convert for_each_wq to use built-in list check ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
[RFC 5/6] x86/pci: Pass lockdep condition to pcm_mmcfg_list iterator ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
[RFC 6/6] acpi: Use built-in RCU list checking for acpi_ioremaps list ("Joel Fernandes (Google)" <joel@...lfernandes.org>)

June 2 (3 messages)

Re: [RFC 2/6] ipv4: add lockdep condition to fix for_each_entry (Pavel Machek <pavel@...x.de>)
Re: [RFC 2/6] ipv4: add lockdep condition to fix for_each_entry (Joel Fernandes <joel@...lfernandes.org>)
Re: [RFC 2/6] ipv4: add lockdep condition to fix for_each_entry (Joel Fernandes <joel@...lfernandes.org>)

June 3 (7 messages)

Re: [RFC 2/6] ipv4: add lockdep condition to fix for_each_entry (Pavel Machek <pavel@...x.de>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Peter Zijlstra <peterz@...radead.org>)
Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
Re: [RFC PATCH v2] powerpc/xmon: restrict when kernel is locked down (Andrew Donnellan <ajd@...ux.ibm.com>)
Re: [RFC 2/6] ipv4: add lockdep condition to fix for_each_entry (Joel Fernandes <joel@...lfernandes.org>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Joel Fernandes <joel@...lfernandes.org>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Joel Fernandes <joel@...lfernandes.org>)

June 4 (10 messages)

Re: [RFC PATCH v2] powerpc/xmon: restrict when kernel is locked down (Christopher M Riedl <cmr@...ormatik.wtf>)
Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time (Kees Cook <keescook@...omium.org>)
Re: [RFC PATCH v2] powerpc/xmon: restrict when kernel is locked down (Andrew Donnellan <ajd@...ux.ibm.com>)
Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time (Kaiwan N Billimoria <kaiwan@...wantech.com>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Steven Rostedt <rostedt@...dmis.org>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Rasmus Villemoes <linux@...musvillemoes.dk>)
Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
Get involved (Romain Perier <romain.perier@...il.com>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Joel Fernandes <joel@...lfernandes.org>)
Re: [RFC 1/6] rcu: Add support for consolidated-RCU reader checking (Joel Fernandes <joel@...lfernandes.org>)

June 5 (5 messages)

Re: [RFC 4/6] workqueue: Convert for_each_wq to use built-in list check (Daniel Jordan <daniel.m.jordan@...cle.com>)
Re: [PATCH v5 2/3] mm: init: report memory auto-initialization features at boot time (Kaiwan N Billimoria <kaiwan@...wantech.com>)
[PATCH] lib/test_stackinit: Handle Clang auto-initialization pattern (Kees Cook <keescook@...omium.org>)
Re: [PATCH] lib/test_stackinit: Handle Clang auto-initialization pattern (Ard Biesheuvel <ard.biesheuvel@...aro.org>)
Re: [RFC 4/6] workqueue: Convert for_each_wq to use built-in list check (Joel Fernandes <joel@...lfernandes.org>)

June 7 (12 messages)

[PATCH v6 1/3] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v6 2/3] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
[PATCH v6 3/3] lib: introduce test_meminit module (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v6 2/3] mm: init: report memory auto-initialization features at boot time (Kees Cook <keescook@...omium.org>)
Re: [PATCH v6 3/3] lib: introduce test_meminit module (Kees Cook <keescook@...omium.org>)
Re: [PATCH v6 1/3] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
[PATCH 4.19 68/73] x86/ftrace: Set trampoline pages as executable (Greg Kroah-Hartman <gregkh@...uxfoundation.org>)
[PATCH 4.19 69/73] x86/kprobes: Set instruction page as executable (Greg Kroah-Hartman <gregkh@...uxfoundation.org>)
[PATCH 5.1 85/85] x86/kprobes: Set instruction page as executable (Greg Kroah-Hartman <gregkh@...uxfoundation.org>)
Re: Get involved (Romain Perier <romain.perier@...il.com>)
Re: Get involved (Shyam Saini <mayhs11saini@...il.com>)
Re: Get involved (Romain Perier <romain.perier@...il.com>)

June 8 (4 messages)

Re: Get involved (Kees Cook <keescook@...omium.org>)
Re: Get involved (Shyam Saini <mayhs11saini@...il.com>)
Re: Get involved (Romain Perier <romain.perier@...il.com>)
Re: Get involved (Shyam Saini <mayhs11saini@...il.com>)

June 10 (17 messages)

Regarding add detection for double-reads ("Khajapasha, Mohammed" <mohammed.khajapasha@...el.com>)
Re: Regarding add detection for double-reads (Kees Cook <keescook@...omium.org>)
[PATCH 1/5] x86/vsyscall: Remove the vsyscall=native documentation (Andy Lutomirski <luto@...nel.org>)
[PATCH 2/5] x86/vsyscall: Add a new vsyscall=xonly mode (Andy Lutomirski <luto@...nel.org>)
[PATCH 3/5] x86/vsyscall: Document odd #PF's error code for vsyscalls (Andy Lutomirski <luto@...nel.org>)
[PATCH 4/5] selftests/x86/vsyscall: Verify that vsyscall=none blocks execution (Andy Lutomirski <luto@...nel.org>)
[PATCH 5/5] x86/vsyscall: Change the default vsyscall mode to xonly (Andy Lutomirski <luto@...nel.org>)
Re: [PATCH 3/5] x86/vsyscall: Document odd #PF's error code for vsyscalls (Kees Cook <keescook@...omium.org>)
Re: [PATCH 2/5] x86/vsyscall: Add a new vsyscall=xonly mode (Kees Cook <keescook@...omium.org>)
Re: [PATCH 5/5] x86/vsyscall: Change the default vsyscall mode to xonly (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 00/12] x86: PIE support to extend KASLR randomization (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 04/12] x86: relocate_kernel - Adapt assembly for PIE support (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 05/12] x86/entry/64: Adapt assembly for PIE support (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 06/12] x86: pm-trace - Adapt assembly for PIE support (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 09/12] x86/boot/64: Adapt assembly for PIE support (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 08/12] x86/acpi: Adapt assembly for PIE support (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 10/12] x86/power/64: Adapt assembly for PIE support (Kees Cook <keescook@...omium.org>)

June 11 (6 messages)

[PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Shyam Saini <shyam.saini@...rulasolutions.com>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Kees Cook <keescook@...omium.org>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Andrew Morton <akpm@...ux-foundation.org>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Shyam Saini <mayhs11saini@...il.com>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Andrew Morton <akpm@...ux-foundation.org>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Shyam Saini <mayhs11saini@...il.com>)

June 12 (19 messages)

Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Alexei Starovoitov <alexei.starovoitov@...il.com>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Andreas Dilger <adilger@...ger.ca>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Andreas Dilger <adilger@...ger.ca>)
[RFC 00/10] Process-local memory allocations for hiding KVM secrets (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 01/10] x86/mm/kaslr: refactor to use enum indices for regions (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 02/10] x86/speculation, mm: add process local virtual memory region (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 03/10] x86/mm, mm,kernel: add teardown for process-local memory to mm cleanup (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 04/10] mm: allocate virtual space for process-local memory (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 05/10] mm: allocate/release physical pages for process-local memory (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 06/10] kvm/x86: add support for storing vCPU state in process-local memory (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 07/10] kvm, vmx: move CR2 context switch out of assembly path (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 08/10] kvm, vmx: move register clearing out of assembly path (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 09/10] kvm, vmx: move gprs to process local memory (Marius Hillenbrand <mhillenb@...zon.de>)
[RFC 10/10] kvm, x86: move guest FPU state into process local memory (Marius Hillenbrand <mhillenb@...zon.de>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Sean Christopherson <sean.j.christopherson@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...capital.net>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...capital.net>)

June 13 (21 messages)

Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Nadav Amit <namit@...are.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Alexander Graf <graf@...zon.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Alexander Graf <graf@...zon.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Alexander Graf <graf@...zon.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Liran Alon <liran.alon@...cle.com>)
[PATCH 0/3] ELF interpretor info: align and add random padding (Yann Droneaud <ydroneaud@...eya.com>)
[PATCH 1/3] binfmt/elf: use functions for stack manipulation (Yann Droneaud <ydroneaud@...eya.com>)
[PATCH 2/3] binfmt/elf: align AT_RANDOM array (Yann Droneaud <ydroneaud@...eya.com>)
[PATCH 3/3] binfmt/elf: randomize padding between ELF interp info (Yann Droneaud <ydroneaud@...eya.com>)
[PATCH 4/3] binfmt/elf: don't expose prandom_u32() state (Yann Droneaud <ydroneaud@...eya.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Nadav Amit <namit@...are.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [PATCH 3/5] x86/vsyscall: Document odd #PF's error code for vsyscalls (Andy Lutomirski <luto@...nel.org>)
Re: [PATCH 2/5] x86/vsyscall: Add a new vsyscall=xonly mode (Andy Lutomirski <luto@...nel.org>)
Re: [PATCH 5/5] x86/vsyscall: Change the default vsyscall mode to xonly (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Sean Christopherson <sean.j.christopherson@...el.com>)

June 14 (9 messages)

Re: [PATCH 5/5] x86/vsyscall: Change the default vsyscall mode to xonly (Kees Cook <keescook@...omium.org>)
[PATCH v2] powerpc/mm: Implement STRICT_MODULE_RWX (Russell Currey <ruscur@...sell.cc>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Thomas Gleixner <tglx@...utronix.de>)
[PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Denis 'GNUtoo' Carikli <GNUtoo@...erdimension.org>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Jann Horn <jannh@...gle.com>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Denis 'GNUtoo' Carikli <GNUtoo@...erdimension.org>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Russell King - ARM Linux admin <linux@...linux.org.uk>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Denis 'GNUtoo' Carikli <GNUtoo@...erdimension.org>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Russell King - ARM Linux admin <linux@...linux.org.uk>)

June 15 (2 messages)

Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Kees Cook <keescook@...omium.org>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Paul Kocialkowski <paul.kocialkowski@...tlin.com>)

June 16 (2 messages)

Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Thomas Gleixner <tglx@...utronix.de>)

June 17 (17 messages)

Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Alexander Graf <graf@...zon.com>)
[PATCH v7 0/3] add init_on_alloc/init_on_free boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v7 2/2] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [PATCH 1/7] General notification queue with user mmap()'able ring buffer (Peter Zijlstra <peterz@...radead.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Nadav Amit <nadav.amit@...il.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Nadav Amit <nadav.amit@...il.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Andy Lutomirski <luto@...nel.org>)
Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets (Dave Hansen <dave.hansen@...el.com>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Andrew Morton <akpm@...ux-foundation.org>)

June 18 (15 messages)

[PATCH v3 3/3] x86/asm: Pin sensitive CR0 bits (Kees Cook <keescook@...omium.org>)
[PATCH v3 0/3] x86/asm: Pin sensitive CR4 and CR0 bits (Kees Cook <keescook@...omium.org>)
[PATCH v3 2/3] x86/asm: Pin sensitive CR4 bits (Kees Cook <keescook@...omium.org>)
[PATCH v3 1/3] lkdtm: Check for SMEP clearing protections (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Andrew Morton <akpm@...ux-foundation.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
Re: [PATCH v3 1/3] lkdtm: Check for SMEP clearing protections (Rasmus Villemoes <linux@...musvillemoes.dk>)
Re: [PATCH v3 1/3] lkdtm: Check for SMEP clearing protections (Kees Cook <keescook@...omium.org>)
Re: [PATCH v3 3/3] x86/asm: Pin sensitive CR0 bits (Jann Horn <jannh@...gle.com>)
RE: Get involved ("Gote, Nitin R" <nitin.r.gote@...el.com>)
Re: Get involved (Jann Horn <jannh@...gle.com>)
Re: [PATCH v3 3/3] x86/asm: Pin sensitive CR0 bits (Peter Zijlstra <peterz@...radead.org>)
Re: [PATCH v3 3/3] x86/asm: Pin sensitive CR0 bits (Kees Cook <keescook@...omium.org>)
Audit and fix all misuse of NLA_STRING: STATUS (Romain Perier <romain.perier@...il.com>)

June 19 (15 messages)

[PATCH v1 01/22] docs: Documentation/*.txt: rename all ReST files to *.rst (Mauro Carvalho Chehab <mchehab+samsung@...nel.org>)
[PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Mauro Carvalho Chehab <mchehab+samsung@...nel.org>)
[PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Mauro Carvalho Chehab <mchehab+samsung@...nel.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Thierry Reding <thierry.reding@...il.com>)
Re: [RFC PATCH v2] powerpc/xmon: restrict when kernel is locked down (Daniel Axtens <dja@...ens.net>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Daniel Vetter <daniel@...ll.ch>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Peter Zijlstra <peterz@...radead.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Mauro Carvalho Chehab <mchehab+samsung@...nel.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Peter Zijlstra <peterz@...radead.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Peter Zijlstra <peterz@...radead.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Peter Zijlstra <peterz@...radead.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Solar Designer <solar@...nwall.com>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Andrea Parri <andrea.parri@...rulasolutions.com>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Mauro Carvalho Chehab <mchehab+samsung@...nel.org>)
Re: [PATCH v1 12/22] docs: driver-api: add .rst files from the main dir (Mauro Carvalho Chehab <mchehab+samsung@...nel.org>)

June 20 (2 messages)

RE: Get involved ("Gote, Nitin R" <nitin.r.gote@...el.com>)
Re: Audit and fix all misuse of NLA_STRING: STATUS (Kees Cook <keescook@...omium.org>)

June 21 (14 messages)

Re: [PATCH v6 1/3] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: Audit and fix all misuse of NLA_STRING: STATUS (Romain Perier <romain.perier@...il.com>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Qian Cai <cai@....pw>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Qian Cai <cai@....pw>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v7 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Denis 'GNUtoo' Carikli <GNUtoo@...erdimension.org>)

June 24 (6 messages)

Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default (Paul Kocialkowski <paul.kocialkowski@...tlin.com>)
[PATCH RFC v2] Convert struct pid count to refcount_t ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
Re: [PATCH RFC v2] Convert struct pid count to refcount_t (Joel Fernandes <joel@...lfernandes.org>)
Re: [PATCH RFC v2] Convert struct pid count to refcount_t (Jann Horn <jannh@...gle.com>)
Re: [PATCH RFC v2] Convert struct pid count to refcount_t (Joel Fernandes <joel@...lfernandes.org>)
Archive kernel-hardening@...ts.openwall.com on lore.kernel.org too (Yann Droneaud <ydroneaud@...eya.com>)

June 25 (27 messages)

Re: [PATCH RFC v2] Convert struct pid count to refcount_t (Peter Zijlstra <peterz@...radead.org>)
Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: [PATCH v6 1/3] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: Detecting the availability of VSYSCALL (Thomas Gleixner <tglx@...utronix.de>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: Audit and fix all misuse of NLA_STRING: STATUS (Romain Perier <romain.perier@...il.com>)
Re: Archive kernel-hardening@...ts.openwall.com on lore.kernel.org too (Solar Designer <solar@...nwall.com>)
Re: Archive kernel-hardening@...ts.openwall.com on lore.kernel.org too (Kees Cook <keescook@...omium.org>)
Re: Archive kernel-hardening@...ts.openwall.com on lore.kernel.org too (Yann Droneaud <ydroneaud@...eya.com>)
Re: Detecting the availability of VSYSCALL (Kees Cook <keescook@...omium.org>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...nel.org>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...nel.org>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...nel.org>)
[PATCH bpf-next v9 07/10] landlock: Add ptrace restrictions (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 05/10] bpf,landlock: Add a new map type: inode (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 04/10] seccomp,landlock: Enforce Landlock programs per process hierarchy (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 10/10] landlock: Add user and kernel documentation for Landlock (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 09/10] bpf,landlock: Add tests for Landlock (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 02/10] bpf: Add eBPF program subtype and is_valid_subtype() verifier (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 00/10] Landlock LSM: Toward unprivileged sandboxing (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 06/10] landlock: Handle filesystem access control (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 03/10] bpf,landlock: Define an eBPF program type for Landlock hooks (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 01/10] fs,security: Add a new file access type: MAY_CHROOT (Mickaël Salaün <mic@...ikod.net>)
[PATCH bpf-next v9 08/10] bpf: Add a Landlock sandbox example (Mickaël Salaün <mic@...ikod.net>)
Re: [PATCH bpf-next v9 05/10] bpf,landlock: Add a new map type: inode (Al Viro <viro@...iv.linux.org.uk>)
Re: [PATCH bpf-next v9 02/10] bpf: Add eBPF program subtype and is_valid_subtype() verifier (Alexei Starovoitov <alexei.starovoitov@...il.com>)

June 26 (23 messages)

Re: [PATCH bpf-next v9 02/10] bpf: Add eBPF program subtype and is_valid_subtype() verifier (Mickaël Salaün <mic@...ikod.net>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: [PATCH v8 0/3] add init_on_alloc/init_on_free boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v8 0/3] add init_on_alloc/init_on_free boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v8 2/2] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...capital.net>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...capital.net>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...capital.net>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...nel.org>)
Re: Detecting the availability of VSYSCALL (Florian Weimer <fweimer@...hat.com>)
Re: Detecting the availability of VSYSCALL (Andy Lutomirski <luto@...nel.org>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Qian Cai <cai@....pw>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
Re: [PATCH RFC v2] Convert struct pid count to refcount_t (Joel Fernandes <joel@...lfernandes.org>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Andrew Morton <akpm@...ux-foundation.org>)
Re: Audit and fix all misuse of NLA_STRING: STATUS (Kees Cook <keescook@...omium.org>)

June 27 (43 messages)

[PATCH v2 1/8] x86/vsyscall: Remove the vsyscall=native documentation (Andy Lutomirski <luto@...nel.org>)
[PATCH v2 2/8] x86/vsyscall: Add a new vsyscall=xonly mode (Andy Lutomirski <luto@...nel.org>)
[PATCH v2 4/8] x86/vsyscall: Document odd SIGSEGV error code for vsyscalls (Andy Lutomirski <luto@...nel.org>)
[PATCH v2 5/8] selftests/x86/vsyscall: Verify that vsyscall=none blocks execution (Andy Lutomirski <luto@...nel.org>)
[PATCH v2 6/8] x86/vsyscall: Change the default vsyscall mode to xonly (Andy Lutomirski <luto@...nel.org>)
[PATCH v2 8/8] selftests/x86: Add a test for process_vm_readv() on the vsyscall page (Andy Lutomirski <luto@...nel.org>)
[PATCH v2 7/8] x86/vsyscall: Add __ro_after_init to global variables (Andy Lutomirski <luto@...nel.org>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: Regarding have kfree() (and related) set the pointer to NULL too ("Gote, Nitin R" <nitin.r.gote@...el.com>)
Re: Regarding have kfree() (and related) set the pointer to NULL too (Vegard Nossum <vegard.nossum@...il.com>)
[PATCH v9 0/3] add init_on_alloc/init_on_free boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v9 2/2] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
Re: [PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Qian Cai <cai@....pw>)
Re: [PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Michal Hocko <mhocko@...nel.org>)
Fwd: Audit and fix all misuse of NLA_STRING: STATUS (Romain Perier <romain.perier@...il.com>)
Re: [PATCH bpf-next v9 05/10] bpf,landlock: Add a new map type: inode (Mickaël Salaün <mickael.salaun@....gouv.fr>)
Re: Regarding have kfree() (and related) set the pointer to NULL too (Kees Cook <keescook@...omium.org>)
Re: [PATCH v8 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
Re: [PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Kees Cook <keescook@...omium.org>)
Re: [PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Qian Cai <cai@....pw>)
Re: Archive kernel-hardening@...ts.openwall.com on lore.kernel.org too (Yann Droneaud <ydroneaud@...eya.com>)
Re: [PATCH bpf-next v9 05/10] bpf,landlock: Add a new map type: inode (Al Viro <viro@...iv.linux.org.uk>)
Re: Archive kernel-hardening@...ts.openwall.com on lore.kernel.org too (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 1/8] x86/vsyscall: Remove the vsyscall=native documentation (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 2/8] x86/vsyscall: Add a new vsyscall=xonly mode (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 4/8] x86/vsyscall: Document odd SIGSEGV error code for vsyscalls (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 5/8] selftests/x86/vsyscall: Verify that vsyscall=none blocks execution (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 6/8] x86/vsyscall: Change the default vsyscall mode to xonly (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 7/8] x86/vsyscall: Add __ro_after_init to global variables (Kees Cook <keescook@...omium.org>)
Re: [PATCH v2 8/8] selftests/x86: Add a test for process_vm_readv() on the vsyscall page (Kees Cook <keescook@...omium.org>)
Re: [PATCH v9 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (James Morris <jmorris@...ei.org>)
[tip:x86/entry] Documentation/admin: Remove the vsyscall=native documentation (tip-bot for Andy Lutomirski <tipbot@...or.com>)
[tip:x86/entry] x86/vsyscall: Add a new vsyscall=xonly mode (tip-bot for Andy Lutomirski <tipbot@...or.com>)
[tip:x86/entry] x86/vsyscall: Document odd SIGSEGV error code for vsyscalls (tip-bot for Andy Lutomirski <tipbot@...or.com>)
[tip:x86/entry] selftests/x86/vsyscall: Verify that vsyscall=none blocks execution (tip-bot for Andy Lutomirski <tipbot@...or.com>)
[tip:x86/entry] x86/vsyscall: Change the default vsyscall mode to xonly (tip-bot for Andy Lutomirski <tipbot@...or.com>)
[tip:x86/entry] x86/vsyscall: Add __ro_after_init to global variables (tip-bot for Andy Lutomirski <tipbot@...or.com>)
[tip:x86/entry] selftests/x86: Add a test for process_vm_readv() on the vsyscall page (tip-bot for Andy Lutomirski <tipbot@...or.com>)

June 28 (8 messages)

[PATCH v10 0/3] add init_on_alloc/init_on_free boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v10 1/2] mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options (Alexander Potapenko <glider@...gle.com>)
[PATCH v10 2/2] mm: init: report memory auto-initialization features at boot time (Alexander Potapenko <glider@...gle.com>)
[PATCH] checkpatch: Added warnings in favor of strscpy(). (Nitin Gote <nitin.r.gote@...el.com>)
Re: [PATCH bpf-next v9 05/10] bpf,landlock: Add a new map type: inode (Mickaël Salaün <mickael.salaun@....gouv.fr>)
Re: [PATCH] checkpatch: Added warnings in favor of strscpy(). (Kees Cook <keescook@...omium.org>)
[PATCH v2] Convert struct pid count to refcount_t ("Joel Fernandes (Google)" <joel@...lfernandes.org>)
Re: [PATCH v2] Convert struct pid count to refcount_t (Kees Cook <keescook@...omium.org>)

June 29 (4 messages)

Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Alexey Dobriyan <adobriyan@...il.com>)
Re: [PATCH RFC v2] Convert struct pid count to refcount_t (Andrea Parri <andrea.parri@...rulasolutions.com>)
Re: [PATCH] checkpatch: Added warnings in favor of strscpy(). (Stephen Kitt <steve@....org>)
Re: [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro (Joe Perches <joe@...ches.com>)

301 messages

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.