From: Con Kolivas <kernel@kolivas.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>,
Chris Wright <chrisw@osdl.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
ck list <ck@vds.kolivas.org>
Subject: Re: [PATCH] Sample fix for hyperthread exploit
Date: Thu, 2 Jun 2005 12:57:51 +1000 [thread overview]
Message-ID: <200506021257.51662.kernel@kolivas.org> (raw)
In-Reply-To: <20050602024924.GD27174@elte.hu>
On Thu, 2 Jun 2005 12:49 pm, Ingo Molnar wrote:
> * Arjan van de Ven <arjan@infradead.org> wrote:
> > > Also, uid is not sufficient. Something more comprehensive (like
> > > ability to ptrace) would be appropriate.
> >
> > I would go a lot simpler. App says "I want exclusivity" via pctl and
> > NOTHING runs on the other half. Well maybe with exceptions of
> > processes that share the mm with the exclusive one (in practice
> > "threads") since those could just read the memory anyway.
>
> this has the disadvantage of needing changes in the security apps.
> Basing this off the uid (or the ability to ptrace) makes it at least
> automatic - but introduces a permanent penalty not only on multiuser
> boxes, but on basically any server box that runs multiple services.
The performance penalty of the sample patch without extra communication or
code would be substantial and I should make it clear to any onlookers that it
is not recommended you use it in any real environment.
Cheers,
Con
next prev parent reply other threads:[~2005-06-02 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 11:58 [PATCH] Sample fix for hyperthread exploit Con Kolivas
2005-06-01 12:06 ` Arjan van de Ven
2005-06-01 12:13 ` Con Kolivas
2005-06-01 17:25 ` Chris Wright
2005-06-01 19:29 ` Arjan van de Ven
2005-06-02 2:49 ` Ingo Molnar
2005-06-02 2:57 ` Con Kolivas [this message]
2005-06-02 6:28 ` Amit Shah
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=200506021257.51662.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=arjan@infradead.org \
--cc=chrisw@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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