linux-um archives
 help / color / mirror / Atom feed
From: "Tiwei Bie" <tiwei.btw@antgroup.com>
To: Benjamin Berg <benjamin@sipsolutions.net>, linux-um@lists.infradead.org
Subject: Re: [PATCH 00/12] Rework stub syscall and page table handling
Date: Mon, 22 Apr 2024 20:08:15 +0800	[thread overview]
Message-ID: <f647fa8f-6cc8-4e8e-9c1c-27b9161f3fdb@antgroup.com> (raw)
In-Reply-To: <4aeca286d181797b7fb02a7fea6bc62a8f616589.camel@sipsolutions.net>

On 4/22/24 3:41 PM, Benjamin Berg wrote:
> On Mon, 2024-04-22 at 10:35 +0800, Tiwei Bie wrote:
>> On 4/18/24 5:23 PM, benjamin@sipsolutions.net wrote:
>>> From: Benjamin Berg <benjamin.berg@intel.com>
>>>
>>> This patchset reworks the stub syscall handling and also redos how page
>>> table updates are tracked and synchronized. Some of this originated in
>>> the SECCOMP patchset, but it became clear that these refactorings make
>>> sense independently as they result in a considerably fewer page faults.
>>
>> I saw your SECCOMP patchset. It's pretty cool! Just wondering if you're about
>> to post a new version soon. :)
> 
> I am planning to work on it again, but it is not very high on my
> priority list. So, could be quite soon or some months :-)
> 
> In the ARM support thread ("UML for arm64"), there were some ideas to
> use FD passing in order to protect memory mappings better. Doing that
> should allow the SECCOMP approach to scale to SMP and will also
> simplify the security model.
> 
> Making those changes will take a bit of thought and experimentation.
> Nothing really big though, it pretty much boils down to using sockets
> for (some of) the synchronization and replacing mprotect with mmap so
> the FD can authorize the operation.

Cool. Thanks for the details! Looking forward to your new version. :)

Regards,
Tiwei


      reply	other threads:[~2024-04-22 12:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  9:23 [PATCH 00/12] Rework stub syscall and page table handling benjamin
2024-04-18  9:23 ` [PATCH 01/12] um: Remove stub-data.h include from common-offsets.h benjamin
2024-04-18  9:23 ` [PATCH 02/12] um: Create signal stack memory assignment in stub_data benjamin
2024-04-18  9:23 ` [PATCH 03/12] um: Add generic stub_syscall6 function benjamin
2024-04-18  9:23 ` [PATCH 04/12] um: Rework syscall handling benjamin
2024-04-18  9:23 ` [PATCH 05/12] um: compress memory related stub syscalls while adding them benjamin
2024-04-18  9:23 ` [PATCH 06/12] um: remove LDT support benjamin
2024-04-18  9:23 ` [PATCH 07/12] um: remove copy_context_skas0 benjamin
2024-04-18  9:23 ` [PATCH 08/12] um: Delay flushing syscalls until the thread is restarted benjamin
2024-04-18  9:23 ` [PATCH 09/12] um: Do not flush MM in flush_thread benjamin
2024-04-18  9:23 ` [PATCH 10/12] um: remove force_flush_all from fork_handler benjamin
2024-04-18  9:23 ` [PATCH 11/12] um: simplify and consolidate TLB updates benjamin
2024-04-18  9:23 ` [PATCH 12/12] um: refactor TLB update handling benjamin
2024-04-22  2:51   ` Tiwei Bie
2024-04-22  7:22     ` Benjamin Berg
2024-04-22  7:51       ` Anton Ivanov
2024-04-22  2:35 ` [PATCH 00/12] Rework stub syscall and page table handling Tiwei Bie
2024-04-22  7:41   ` Benjamin Berg
2024-04-22 12:08     ` Tiwei Bie [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=f647fa8f-6cc8-4e8e-9c1c-27b9161f3fdb@antgroup.com \
    --to=tiwei.btw@antgroup.com \
    --cc=benjamin@sipsolutions.net \
    --cc=linux-um@lists.infradead.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