From: Deepak Gupta <debug@rivosinc.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"szabolcs.nagy@arm.com" <szabolcs.nagy@arm.com>,
"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"kito.cheng@sifive.com" <kito.cheng@sifive.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Shadow stack enabling from dynamic loader v/s kernel on exec
Date: Tue, 28 Nov 2023 12:29:22 -0800 [thread overview]
Message-ID: <ZWZNothlvzQKStOc@debug.ba.rivosinc.com> (raw)
In-Reply-To: <ZWXiYCs45Ryb6UMf@finisterre.sirena.org.uk>
On Tue, Nov 28, 2023 at 12:51:44PM +0000, Mark Brown wrote:
>On Mon, Nov 27, 2023 at 05:41:16PM +0000, Edgecombe, Rick P wrote:
>> On Wed, 2023-11-22 at 16:19 -0800, Deepak Gupta wrote:
>
>> Thanks. As we look at adding some final glibc support, I've wondered if
>> there might be enough topics to warrant an occasional meeting to
>> discuss stuff like this. I'd also like to discuss the shadow stack life
>> cycle issues (uncontext, etc), alt shadow stacks and all of the
>> compatibility last mile problems. Towards the goal of avoiding
>> unnecessary divergence on app developer expectations.
>
>It'd definitely be good to ensure we're coordinating well, I'd be
>willing to give it a go.
Same here.
prev parent reply other threads:[~2023-11-28 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 0:19 Shadow stack enabling from dynamic loader v/s kernel on exec Deepak Gupta
2023-11-25 11:35 ` Mark Brown
2023-11-27 17:32 ` Edgecombe, Rick P
2023-11-28 13:55 ` Mark Brown
2023-11-27 17:41 ` Edgecombe, Rick P
2023-11-28 12:51 ` Mark Brown
2023-11-28 20:29 ` Deepak Gupta [this message]
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=ZWZNothlvzQKStOc@debug.ba.rivosinc.com \
--to=debug@rivosinc.com \
--cc=broonie@kernel.org \
--cc=hjl.tools@gmail.com \
--cc=keescook@chromium.org \
--cc=kito.cheng@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=szabolcs.nagy@arm.com \
/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