[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <44186.1705797812@cvs.openbsd.org>
Date: Sat, 20 Jan 2024 17:43:32 -0700
From: "Theo de Raadt" <deraadt@...nbsd.org>
To: Jeff Xu <jeffxu@...omium.org>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Stephen Röttger <sroettger@...gle.com>,
Jeff Xu <jeffxu@...gle.com>, akpm@...ux-foundation.org,
keescook@...omium.org, jannh@...gle.com, willy@...radead.org,
gregkh@...uxfoundation.org, jorgelo@...omium.org,
groeck@...omium.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-mm@...ck.org,
pedro.falcato@...il.com, dave.hansen@...el.com,
linux-hardening@...r.kernel.org
Subject: Re: [RFC PATCH v3 11/11] mseal:add documentation
Jeff Xu <jeffxu@...omium.org> wrote:
> > Jeff - mind changing the EACESS to EPERM, and we'll have something
> > that is more-or-less compatible between Linux and OpenBSD?
> >
> Sounds Good. I will make the necessary changes in the next version.
Thanks! That is so awesome!
On the OpenBSD side, I am close to landing our madvise / msync changes.
Then we are mostly in sync.
It was on my radar for a year, but delayed because I was ponderingn
blocking the destructive madvise / msync ops on regular non-writeable
pages. These ops remain a page-zero gadget against regular (mutable)
readonly pages, and it bothers me. I've heard rumour this has been used
in a nasty way, and I think the sloppily defined semantics could use
a strict modernization.
Powered by blists - more mailing lists