[lkml]   [1998]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ANNOUNCE: Pset (sysmp) 0.58 for Linux/SMP now available
In article <Pine.LNX.3.96.980817203901.10232A-100000@dragon.bogus>,
Andrea Arcangeli <> writes:
> On Mon, 17 Aug 1998, Tim Hockin wrote:
>> their IRIX 6.4 kernel) for Linux. This enables users to determine which
>> processor or set of processors a process may run on. Possible uses
>> include forcing threads to seperate processors, timings, security (a
>> `root' only CPU?) and probably more.

> I can' t see how can be more secure to have a root process running only in
> a CPU instead of allow the kernel to run it in the fist idle.

> Could you explian me how could be more secure?

For example if you compute a cryptographic algorithm in the root
process then some information leaks over thread/process boundaries
(e.g. cycle counters, or cache line information etc.) and could be
used to recover the secret key. If Linux wanted B1 level security then
this would have to be addressed.

Search the web for 'side-chanel cryptoanalysis' or 'timing attacks'
for more information about this. e.g.

Note that the leaking of the cycle counters on Intel could be easily
fixed: Intel has a flag to only allow reading them in superuser mode -
it would require an addition to prctl() [or trapping the resulting
exception of a user space read, but that is ugly]. This would result
in more reliable cycle counters too, because they could be saved between
threads - currently they're all system global.

> Also how can be it more efficient for multithreading?

At least it is required for lots of hard real time applications.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.053 / U:1.572 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site