On Tue, May 24, 2011 at 11:25 AM, Thomas Gleixner <firstname.lastname@example.org> wrote:
> On Tue, 24 May 2011, Peter Zijlstra wrote:
>> On Tue, 2011-05-24 at 10:59 -0500, Will Drewry wrote:
>> > include/linux/ftrace_event.h | 4 +-
>> > include/linux/perf_event.h | 10 +++++---
>> > kernel/perf_event.c | 49
>> > +++++++++++++++++++++++++++++++++++++---
>> > kernel/seccomp.c | 8 ++++++
>> > kernel/trace/trace_syscalls.c | 27 +++++++++++++++++-----
>> > 5 files changed, 82 insertions(+), 16 deletions(-)
>> I strongly oppose to the perf core being mixed with any sekurity voodoo
>> (or any other active role for that matter).
> Amen. We have enough crap to cleanup in perf/ftrace already, so we
> really do not need security magic added to it.
Thanks for the quick responses!
I agree, but I'm left a little bit lost now w.r.t. the comments around
reusing the ABI. If perf doesn't make sense (which certainly seems
wrong from a security interface perspective), then the preexisting
ABIs I know of for this case are as follows:
- prctl(PR_SET_SECCOMP* (or /proc/...)
Both would require expansion. The latter was reused by the original
patch series. The former doesn't expose much in the way of per-task
event filtering -- ftrace_pids doesn't translate well to
ftrace_syscall_enter-based enforcement. I'd expect we'd need
ftrace_event_call->task_events (like ->perf_events), and either
explore them in ftrace_syscall_enter or add a new tracepoint handler,
ftrace_task_syscall_enter, via something like TRACE_REG_TASK_REGISTER.
It could then do whatever it wanted with the successful or
unsuccessful matching against predicates, stacking or not, which could
be used for a seccomp-like mechanism. However, bubbling that change
up to the non-existent interfaces in debug/tracing could be a
challenge too (Registration would require an alternate flow like perf
to call TRACE_REG_*? Do they become
This is all just a matter of programming... but at this point, I'm not
seeing the clear shared path forward. Even with per-task ftrace
access in debug/tracing, that would introduce a reasonably large
change to the system and add a new ABI, albeit in debug/tracing. If
the above (or whatever the right approach is) comes into existence,
then any prctl(PR_SET_SECCOMP) ABI could have the backend
implementation to modify the same data. I'm not putting it like this
to say that I'm designing to be obsolete, but to show that the defined
interface wouldn't conflict if ftrace does overlap more in the future.
Given the importance of a clearly defined interface for security
functionality, I'd be surprised to see all the pieces come together in
the near future in such a way that a transition would be immediately
possible -- I'm not even sure what the ftrace roadmap really is!
Would it be more desirable to put a system call filtering interface on
a miscdev (like /dev/syscall_filter) instead of in /proc or prctl (and
not reuse seccomp at all)? I'm not clear what the onus is to justify
a change in the different ABI areas, but I see system call filtering
as an important piece of system security and would like to determine
if there is a viable path forward, or if this will need to be
revisited in another 2 years.