linux-kernel - Re: disabling group leader perf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100912064612.GA1582@ucw.cz>
Date:	Sun, 12 Sep 2010 08:46:13 +0200
From:	Pavel Machek <pavel@....cz>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Avi Kivity <avi@...hat.com>, Pekka Enberg <penberg@...helsinki.fi>,
	Tom Zanussi <tzanussi@...il.com>,
	Fr?d?ric Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-perf-users@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: disabling group leader perf_event

Hi!

> > >>Is this a roundabout way of saying "jit"?
> > >Partly. I'm not sure we want to actually upload programs in bytecode
> > >form. ASCII is just fine - just like a .gz Javascript is fine for web
> > >apps. (and in most cases compresses down better than the bytecode
> > >equivalent)
> > >
> > >So a clear language (the simpler initially the better) plus an in-kernel
> > >compiler.
> > >
> > >This could be used for far more than just instrumentation: IMO security
> > >policies could be expressed in such a way. (Simplified, they are quite
> > >similar to filters installed on syscall entry/exit, with the ability of
> > >the filter to influence whether the syscall is performed.)
> > 
> > For me the requirements are:
> > - turing complete (more than just filters)
> 
> Yep. Filters are obviously just basically expressions.
> 
> Conditions and variables can be added. Maybe loops too in simpler forms 
> - as long as we can prove halting - or maybe with a runtime abort 
> mechanism.
> 
> > - easy interface to kernel APIs (like hrtimers)
> > - safe to use by untrusted users
> 
> Yep.
> 
> > The actual language doesn't really matter.
> 
> There are 3 basic categories:
> 
>  1- Most (least abstract) specific code: a block of bytecode in the form 
>     of a simplified, executable, kernel-checked x86 machine code block - 
>     this is also the fastest form. [yes, this is actually possible.]

Well... if we want to be a bit x86-entric.... can we just reuse ACPI
interpretter?

Plus, TOMOYO actually has a language inside... AppArmor actually has
something, too, but iirc it is only as powerful as regexps.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/