From: David Laight <David.Laight@ACULAB.COM>
To: "'jeffxu@chromium.org'" <jeffxu@chromium.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"jannh@google.com" <jannh@google.com>,
"sroettger@google.com" <sroettger@google.com>,
"willy@infradead.org" <willy@infradead.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "jeffxu@google.com" <jeffxu@google.com>,
"jorgelo@chromium.org" <jorgelo@chromium.org>,
"groeck@chromium.org" <groeck@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"surenb@google.com" <surenb@google.com>,
"alex.sierra@amd.com" <alex.sierra@amd.com>,
"apopple@nvidia.com" <apopple@nvidia.com>,
"aneesh.kumar@linux.ibm.com" <aneesh.kumar@linux.ibm.com>,
"axelrasmussen@google.com" <axelrasmussen@google.com>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"david@redhat.com" <david@redhat.com>,
"dwmw@amazon.co.uk" <dwmw@amazon.co.uk>,
"ying.huang@intel.com" <ying.huang@intel.com>,
"hughd@google.com" <hughd@google.com>,
"joey.gouly@arm.com" <joey.gouly@arm.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
"lstoakes@gmail.com" <lstoakes@gmail.com>,
"mawupeng1@huawei.com" <mawupeng1@huawei.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"namit@vmware.com" <namit@vmware.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"shr@devkernel.io" <shr@devkernel.io>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"xiujianfeng@huawei.com" <xiujianfeng@huawei.com>,
"yu.ma@intel.com" <yu.ma@intel.com>,
"zhangpeng362@huawei.com" <zhangpeng362@huawei.com>,
"dave.hansen@intel.com" <dave.hansen@intel.com>,
"luto@kernel.org" <luto@kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>
Subject: RE: [RFC PATCH v2 0/8] Introduce mseal() syscall
Date: Thu, 19 Oct 2023 09:19:29 +0000 [thread overview]
Message-ID: <b3508782e1304074b4b43040be2d1f1b@AcuMS.aculab.com> (raw)
In-Reply-To: <20231017090815.1067790-1-jeffxu@chromium.org>
From: jeffxu@chromium.org
> Sent: 17 October 2023 10:08
>
> This patchset proposes a new mseal() syscall for the Linux kernel.
I'm sure you can give it a better name, there isn't a 6 character
limit on identifiers!
FWIW you could also use mprotect(addr, len, IMMUTABLE);
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2023-10-19 9:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 9:08 jeffxu
2023-10-17 9:08 ` [RFC PATCH v2 1/8] mseal: Add mseal(2) syscall jeffxu
2023-10-17 15:45 ` Randy Dunlap
2023-10-17 9:08 ` [RFC PATCH v2 2/8] mseal: Wire up mseal syscall jeffxu
2023-10-17 9:08 ` [RFC PATCH v2 3/8] mseal: add can_modify_mm and can_modify_vma jeffxu
2023-10-17 9:08 ` [RFC PATCH v2 4/8] mseal: Check seal flag for mprotect(2) jeffxu
2023-10-17 9:08 ` [RFC PATCH v2 5/8] mseal: Check seal flag for munmap(2) jeffxu
2023-10-17 16:54 ` Linus Torvalds
2023-10-18 15:08 ` Jeff Xu
2023-10-18 17:14 ` Jeff Xu
2023-10-18 18:27 ` Linus Torvalds
2023-10-18 19:07 ` Jeff Xu
2023-10-17 9:08 ` [RFC PATCH v2 6/8] mseal: Check seal flag for mremap(2) jeffxu
2023-10-20 13:56 ` Muhammad Usama Anjum
2023-10-17 9:08 ` [RFC PATCH v2 7/8] mseal:Check seal flag for mmap(2) jeffxu
2023-10-17 17:04 ` Linus Torvalds
2023-10-17 17:43 ` Linus Torvalds
2023-10-18 7:01 ` Jeff Xu
2023-10-19 7:27 ` Stephen Röttger
2023-10-17 9:08 ` [RFC PATCH v2 8/8] selftest mm/mseal mprotect/munmap/mremap/mmap jeffxu
2023-10-20 14:24 ` Muhammad Usama Anjum
2023-10-20 15:23 ` Peter Zijlstra
2023-10-20 16:33 ` Muhammad Usama Anjum
2023-10-19 9:19 ` David Laight [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=b3508782e1304074b4b43040be2d1f1b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alex.sierra@amd.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=axelrasmussen@google.com \
--cc=ben@decadent.org.uk \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jeffxu@google.com \
--cc=joey.gouly@arm.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linmiaohe@huawei.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=luto@kernel.org \
--cc=mawupeng1@huawei.com \
--cc=namit@vmware.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=ryan.roberts@arm.com \
--cc=shr@devkernel.io \
--cc=sroettger@google.com \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=xiujianfeng@huawei.com \
--cc=ying.huang@intel.com \
--cc=yu.ma@intel.com \
--cc=zhangpeng362@huawei.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