From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Fr??d??ric Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>,
systemtap@sources.redhat.com,
dle-develop@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
utrace-devel@redhat.com,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: add utrace tree
Date: Sat, 23 Jan 2010 12:03:00 -0000 [thread overview]
Message-ID: <20100123120301.GD7828@redhat.com> (raw)
In-Reply-To: <20100123060401.GB19399@elte.hu>
Hi -
On Sat, Jan 23, 2010 at 07:04:01AM +0100, Ingo Molnar wrote:
> [...] Also, if any systemtap person is interested in helping us
> create a more generic filter engine out of the current ftrace filter
> engine (which is really a precursor of a safe, sandboxed in-kernel
> script engine), that would be excellent as well. [...]
Thank you for the invitation.
> More could be done - a simple C-like set of function perhaps - some minimal
> per probe local variable state, etc. (perhaps even looping as well, with a
> limit on number of predicament executions per filter invocation.)
Yes, at some point when such bytecode intepreter gets rich enough, one
may not need the translated-to-C means of running scripts.
> ( _Such_ a facility, could then perhaps be used to allow applications access
> to safe syscall sandboxing techniques: i.e. a programmable seccomp concept
> in essence, controlled via ASCII space filter expressions [...]
> IMHO that would be a superior concept for security modules too [...]
>
> [...] specific functionality with an immediately visible upside,
> with no need for opaque hooks.
This OTOH seem like rather a stretch. If one claims that "opaque
hooks" are bad, so instead have hooks that jump not to auditable C
code but an bytecode interpreter? And have the bytecodes be uploaded
from userspace? How is this supposed to produce "transparency" from
the kernel/hook point of view?
- FChE
next prev parent reply other threads:[~2010-01-23 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100121013822.28781960.sfr@canb.auug.org.au>
[not found] ` <20100122111747.3c224dfd.sfr@canb.auug.org.au>
[not found] ` <20100121163004.8779bd69.akpm@linux-foundation.org>
[not found] ` <20100121163145.7e958c3f.akpm@linux-foundation.org>
[not found] ` <20100122005147.GD22003@redhat.com>
[not found] ` <20100121170541.7425ff10.akpm@linux-foundation.org>
[not found] ` <20100122012516.GE22003@redhat.com>
[not found] ` <alpine.LFD.2.00.1001211729080.13231@localhost.localdomain>
[not found] ` <20100122022255.GF22003@redhat.com>
[not found] ` <alpine.LFD.2.00.1001211826060.13231@localhost.localdomain>
2010-01-23 6:04 ` Ingo Molnar
2010-01-23 12:03 ` Frank Ch. Eigler [this message]
2010-01-24 16:37 ` Thomas Gleixner
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=20100123120301.GD7828@redhat.com \
--to=fche@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tzanussi@gmail.com \
--cc=utrace-devel@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).