From: Kees Cook <keescook@chromium.org>
To: Roy Yang <royyang@google.com>
Cc: akpm@linux-foundation.org, alex.popov@linux.com,
ard.biesheuvel@linaro.org, catalin.marinas@arm.com,
corbet@lwn.net, david@redhat.com, elena.reshetova@intel.com,
glider@google.com, jannh@google.com,
kernel-hardening@lists.openwall.com,
linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, luto@kernel.org, mark.rutland@arm.com,
peterz@infradead.org, rdunlap@infradead.org, rppt@linux.ibm.com,
tglx@linutronix.de, vbabka@suse.cz, will@kernel.org,
x86@kernel.org
Subject: Re: [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall
Date: Thu, 1 Apr 2021 14:46:23 -0700 [thread overview]
Message-ID: <202104011442.B20F2BAFC@keescook> (raw)
In-Reply-To: <20210401191744.1685896-1-royyang@google.com>
On Thu, Apr 01, 2021 at 12:17:44PM -0700, Roy Yang wrote:
> Both Android and Chrome OS really want this feature; For Container-Optimized OS, we have customers
> interested in the defense too.
It's pretty close! There are a couple recent comments that need to be
addressed, but hopefully it can land if x86 and arm64 maintainers are
happy v10.
> Change-Id: I1eb1b726007aa8f9c374b934cc1c690fb4924aa3
> --
> 2.31.0.208.g409f899ff0-goog
And to let other folks know, I'm guessing this email got sent with git
send-email to try to get a valid In-Reply-To header, but I guess git
trashed the Subject and ran hooks to generate a Change-Id UUID.
I assume it's from following the "Reply instructions" at the bottom of:
https://lore.kernel.org/lkml/20210330205750.428816-1-keescook@chromium.org/
(It seems those need clarification about Subject handling.)
--
Kees Cook
next prev parent reply other threads:[~2021-04-01 21:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 20:57 [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall Kees Cook
2021-03-30 20:57 ` [PATCH v8 1/6] jump_label: Provide CONFIG-driven build state defaults Kees Cook
2021-03-30 20:57 ` [PATCH v8 2/6] init_on_alloc: Optimize static branches Kees Cook
2021-03-30 20:57 ` [PATCH v8 3/6] stack: Optionally randomize kernel stack offset each syscall Kees Cook
2021-03-31 7:53 ` Thomas Gleixner
2021-03-31 21:54 ` Kees Cook
2021-03-31 22:38 ` Thomas Gleixner
2021-04-01 6:31 ` Kees Cook
2021-04-01 8:30 ` Will Deacon
2021-04-01 11:15 ` David Laight
2021-04-01 22:42 ` Kees Cook
2021-03-30 20:57 ` [PATCH v8 4/6] x86/entry: Enable random_kstack_offset support Kees Cook
2021-03-31 7:50 ` Thomas Gleixner
2021-03-30 20:57 ` [PATCH v8 5/6] arm64: entry: " Kees Cook
2021-03-30 20:57 ` [PATCH v8 6/6] lkdtm: Add REPORT_STACK for checking stack offsets Kees Cook
2021-04-01 19:17 ` [PATCH] Where we are for this patch? Roy Yang
2021-04-01 19:48 ` Al Viro
2021-04-01 20:13 ` Theodore Ts'o
2021-04-01 21:46 ` Kees Cook [this message]
2021-04-01 20:49 [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall Roy Yang
2021-04-01 20:59 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202104011442.B20F2BAFC@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=alex.popov@linux.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=elena.reshetova@intel.com \
--cc=glider@google.com \
--cc=jannh@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=royyang@google.com \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).