From: James Morris <jmorris@namei.org>
To: Will Drewry <wad@chromium.org>
Cc: Andrew Lutomirski <luto@mit.edu>,
Kees Cook <keescook@chromium.org>,
james.l.morris@oracle.com, rob@landley.net,
linux-doc@vger.kernel.org, cevans@chromium.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
eparis@redhat.com, fengxj325@gmail.com
Subject: Re: [PATCH 2/3] vsyscall_64: allow SECCOMP_RET_TRACErs to skip
Date: Fri, 10 Aug 2012 19:14:32 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1208101913160.14083@tundra.namei.org> (raw)
In-Reply-To: <CABqD9hYoVNo34oqGh7mCmGZF7nKDC3-d2LD=BLhEUJtM7GbFvQ@mail.gmail.com>
On Sat, 14 Jul 2012, Will Drewry wrote:
> Agreed :) I don't mind making tweaks to get it right, but this only
> matters to users that want to:
> - use seccomp filter
> - with ptrace (or trap with resumption and not sigreturn)
> - of time, gettimeofday, and getcpu
> since they will then have to include quirk management _just_ in case
> their code is linked against something using vsyscall and
> vsyscall=emulate is in effect!
I think these patches came out during the merge window -- is there any
further discussion on them?
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2012-08-10 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 15:32 [PATCH 1/3] vsyscall_64: add missing ifdef CONFIG_SECCOMP Will Drewry
2012-07-14 15:32 ` [PATCH 2/3] vsyscall_64: allow SECCOMP_RET_TRACErs to skip Will Drewry
[not found] ` <CAObL_7GX0q_qywY4g1S2iRZWPS95ar01wtvv9wDW=zswwaZ6fQ@mail.gmail.com>
2012-07-14 15:50 ` Will Drewry
2012-07-14 15:57 ` Will Drewry
2012-07-14 16:15 ` Andrew Lutomirski
2012-07-14 16:21 ` Andrew Lutomirski
2012-07-14 16:55 ` Will Drewry
2012-08-10 9:14 ` James Morris [this message]
2012-08-13 18:17 ` Andrew Lutomirski
2012-07-14 15:32 ` [PATCH 3/3] Documentation: add a caveat for seccomp filter and vsyscall emulation Will Drewry
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=alpine.LRH.2.02.1208101913160.14083@tundra.namei.org \
--to=jmorris@namei.org \
--cc=cevans@chromium.org \
--cc=eparis@redhat.com \
--cc=fengxj325@gmail.com \
--cc=hpa@zytor.com \
--cc=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=rob@landley.net \
--cc=torvalds@linux-foundation.org \
--cc=wad@chromium.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
all inboxes | Powered by JetHome®