public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <shahamit@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: ck@vds.kolivas.org
Subject: Re: [PATCH] Sample fix for hyperthread exploit
Date: Thu, 02 Jun 2005 11:58:45 +0530	[thread overview]
Message-ID: <d7m8u0$ivc$1@sea.gmane.org> (raw)
In-Reply-To: 20050602024924.GD27174@elte.hu

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.

Can this be not limited to just not running any other process on the same
(SMT-enabled) processor (precondition being ability to ptrace)?

Amit.
-- 
Amit Shah
http://amitshah.net/


      parent reply	other threads:[~2005-06-02  6:32 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
2005-06-02  6:28           ` Amit Shah [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='d7m8u0$ivc$1@sea.gmane.org' \
    --to=shahamit@gmail.com \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.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