Re: [RFC] perf: Prevent potential null dereference

From: Arnaldo Carvalho de Melo
Date: Mon Dec 06 2010 - 09:50:09 EST


Em Mon, Dec 06, 2010 at 01:13:21AM +0300, Cyrill Gorcunov escreveu:
> On Thu, Dec 02, 2010 at 08:46:10PM -0200, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Dec 02, 2010 at 11:41:08PM +0100, Frederic Weisbecker escreveu:
> > > On Fri, Dec 03, 2010 at 01:26:05AM +0300, Cyrill Gorcunov wrote:
> > > > In case if there is no memory we might hit null
> > > > dereference on accessing calloc'ed data.
> > > >
> > > > Signed-off-by: Cyrill Gorcunov <gorcunov@xxxxxxxxxx>
> > > > CC: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
> > > > CC: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
> > > > CC: Ingo Molnar <mingo@xxxxxxx>
> > > > CC: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> > > > ---
> ...
> > >
> > > Good.
> > >
> > > As a nit, not that it matters that much because we are very close to the starting code
> > > anyway, but it would be better to propagate the error to the callers.
> >
> > I'm of the opinion that main() should be where exit() is allowed, and
> > even there... return would be better. 8-)
> >
> > - Arnaldo
> >
>
> ok, sorry for delay, it seems the following would be liked
> more than first version ;)
>

Hey, what tree is this agains? I guess tip/master, right? If so, I still
didn't got there :-\

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/