Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 29 Sep 2020 19:47:12 -0400
From: Steven Rostedt <>
To: Kees Cook <>
Cc:, John Wood <>,
 Matthew Wilcox <>, Jonathan Corbet <>,
 Alexander Viro <>, Ingo Molnar <>,
 Peter Zijlstra <>, Juri Lelli <>,
 Vincent Guittot <>, Dietmar Eggemann
 <>, Ben Segall <>, Mel Gorman
 <>, Luis Chamberlain <>, Iurii Zaikin
 <>, James Morris <>, "Serge E. Hallyn"
Subject: Re: [RFC PATCH 3/6] security/fbfam: Use the api to manage

On Thu, 10 Sep 2020 16:33:38 -0700
Kees Cook <> wrote:

> > @@ -1940,6 +1941,7 @@ static int bprm_execve(struct linux_binprm *bprm,
> >  	task_numa_free(current, false);
> >  	if (displaced)
> >  		put_files_struct(displaced);
> > +	fbfam_execve();  
> As mentioned in the other emails, I think this could trivially be
> converted into an LSM: all the hooks are available AFAICT. If you only
> want to introspect execve _happening_, you can use bprm_creds_for_exec
> which is called a few lines above. Otherwise, my prior suggestion ("the
> exec has happened" hook via brpm_cred_committing, etc).

And if its information only, you could just register a callback to the
trace_sched_process_exec() tracepoint and do whatever you want then.

The tracepoints are available for anyone to attach to. Not just tracing.

-- Steve

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.