From: Matthew Wilcox <willy@infradead.org>
To: Paul Gofman <gofmanp@gmail.com>
Cc: Gabriel Krisman Bertazi <krisman@collabora.com>,
Kees Cook <keescook@chromium.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, "H . Peter Anvin" <hpa@zytor.com>,
linux-security-module@vger.kernel.org,
Zebediah Figura <zfigura@codeweavers.com>
Subject: Re: [PATCH RFC] seccomp: Implement syscall isolation based on memory areas
Date: Sun, 31 May 2020 09:49:38 -0700 [thread overview]
Message-ID: <20200531164938.GF19604@bombadil.infradead.org> (raw)
In-Reply-To: <9a512096-7707-3fc6-34ba-22f969c0f964@gmail.com>
On Sun, May 31, 2020 at 03:39:33PM +0300, Paul Gofman wrote:
> > Paul (cc'ed) is the wine expert, but my understanding is that memory
> > allocation and initial program load of the emulated binary will go
> > through wine. It does the allocation and mark the vma accordingly
> > before returning the allocated range to the windows application.
> Yes, exactly. Pretty much any memory allocation which Wine does needs
> syscalls (if those are ever encountered later during executing code from
> those areas) to be trapped by Wine and passed to Wine's implementation
> of the corresponding Windows API function. Linux native libraries
> loading and memory allocations performed by them go outside of Wine control.
I don't like Gabriel's approach very much. Could we do something like
issue a syscall before executing a Windows region and then issue another
syscall when exiting? If so, we could switch the syscall entry point (ie
change MSR_LSTAR). I'm thinking something like a personality() syscall.
But maybe that would be too high an overhead.
next prev parent reply other threads:[~2020-05-31 16:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 5:59 [PATCH RFC] seccomp: Implement syscall isolation based on memory areas Gabriel Krisman Bertazi
2020-05-30 17:30 ` Kees Cook
2020-05-31 5:56 ` Gabriel Krisman Bertazi
2020-05-31 12:39 ` Paul Gofman
2020-05-31 16:49 ` Matthew Wilcox [this message]
2020-05-31 17:10 ` Paul Gofman
2020-05-31 17:31 ` Matthew Wilcox
2020-05-31 18:01 ` Paul Gofman
2020-06-01 17:54 ` Gabriel Krisman Bertazi
2020-06-01 17:53 ` Gabriel Krisman Bertazi
2020-05-30 22:09 ` Andy Lutomirski
2020-05-31 0:26 ` Gabriel Krisman Bertazi
2020-05-31 0:59 ` Andy Lutomirski
2020-05-31 12:56 ` Paul Gofman
2020-05-31 18:10 ` Andy Lutomirski
2020-05-31 18:36 ` Paul Gofman
2020-05-31 18:57 ` Andy Lutomirski
2020-05-31 19:37 ` Paul Gofman
2020-05-31 21:03 ` Andy Lutomirski
2020-06-01 18:06 ` Gabriel Krisman Bertazi
2020-06-01 20:08 ` Kees Cook
2020-06-01 23:18 ` Andy Lutomirski
2020-06-11 19:38 ` Gabriel Krisman Bertazi
2020-05-31 23:33 ` Brendan Shanks
2020-06-01 1:51 ` Andy Lutomirski
2020-06-25 23:14 ` Robert O'Callahan
2020-06-25 23:48 ` Gabriel Krisman Bertazi
2020-06-26 1:03 ` Robert O'Callahan
2020-06-05 6:06 ` Sargun Dhillon
2020-06-01 9:23 Billy Laws
2020-06-01 13:59 ` Andy Lutomirski
2020-06-01 17:48 ` hpa
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=20200531164938.GF19604@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=gofmanp@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tglx@linutronix.de \
--cc=wad@chromium.org \
--cc=zfigura@codeweavers.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;
as well as URLs for NNTP newsgroup(s).