Re: [PATCH] audit: catch possible NULL audit buffers

2012-11-19 Thread Kees Cook
On Mon, Nov 19, 2012 at 2:14 PM, Andrew Morton wrote: > On Mon, 19 Nov 2012 14:00:51 -0800 > Kees Cook wrote: > >> It's possible for audit_log_start() to return NULL. Handle it in the >> various callers. >> >> ... >> >> --- a/kernel/audit.c >> +++ b/kernel/audit.c >> @@ -272,6 +272,8 @@ static in

Re: [PATCH] audit: catch possible NULL audit buffers

2012-11-19 Thread Andrew Morton
On Mon, 19 Nov 2012 14:00:51 -0800 Kees Cook wrote: > It's possible for audit_log_start() to return NULL. Handle it in the > various callers. > > ... > > --- a/kernel/audit.c > +++ b/kernel/audit.c > @@ -272,6 +272,8 @@ static int audit_log_config_change(char *function_name, > int new, int old,

[PATCH] audit: catch possible NULL audit buffers

2012-11-19 Thread Kees Cook
It's possible for audit_log_start() to return NULL. Handle it in the various callers. Signed-off-by: Kees Cook --- This leaves out the change to the audit_seccomp, since I fixed that in a separate patch ("audit: create explicit AUDIT_SECCOMP event type"). --- kernel/audit.c |4 k