Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 22 Aug 2022 13:40:28 -0700
From:   Kees Cook <keescook@chromium.org>
To:     Dave Hansen <dave.hansen@linux.intel.com>
Cc:     Stephen =?iso-8859-1?Q?R=F6ttger?= <sroettger@google.com>,
        x86@kernel.org, linux-kernel@vger.kernel.org
Subject: PKU usage improvements for threads
Message-ID: <202208221331.71C50A6F@keescook>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi!

I was hoping to start a conversation about PKU usage for threads in two
places, which Stephen R?ttger brought to my attention, with the hope of
being able to use these in Chrome:

1) It appears to be a bug that a thread without the correct PK can make
VMAs covered by a separate PK, out from under other threads. (e.g. mmap
a new mapping to wipe out the defined PK for it.) It seems that PK checks
should be made when modifying VMAs.

2) It would be very helpful to have a mechanism for the signal stack to
be PK aware, in the sense that the kernel would switch to a predefined
PK. i.e. having a new interface to sigaltstack() which includes a PK.

Are either of these something the PKU authors have considered? (Or are
there some details we're missing in this area?)

Thanks!

-Kees

-- 
Kees Cook