[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1310753007.2945.7.camel@work-vm>
Date: Fri, 15 Jul 2011 11:03:27 -0700
From: john stultz <johnstul@...ibm.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Willy Tarreau <w@....eu>, Ingo Molnar <mingo@...e.hu>,
"MINOURA Makoto / ?$BL'1: ?$B??" <minoura@...inux.co.jp>,
Andrew Morton <akpm@...ux-foundation.org>,
Faidon Liambotis <paravoid@...ian.org>,
linux-kernel@...r.kernel.org, stable@...nel.org,
Nikola Ciprich <nikola.ciprich@...uxbox.cz>,
seto.hidetoshi@...fujitsu.com,
Hervé Commowick <hcommowick@...sec.fr>,
Rand@...per.es
Subject: Re: 2.6.32.21 - uptime related crashes?
On Fri, 2011-07-15 at 12:02 +0200, Peter Zijlstra wrote:
> On Fri, 2011-07-15 at 10:30 +0200, Peter Zijlstra wrote:
> > On Thu, 2011-07-14 at 17:35 -0700, john stultz wrote:
> > >
> > > Peter/Ingo: Can you take a look at the above and let me know if you find
> > > it too disagreeable?
> >
> > I'm not quite sure of the calling conditions of set_cyc2ns_scale(), but
> > there's two sites in there that do:
> >
> > + local_irq_save(flags);
> >
> > + data = kmalloc(sizeof(*data), GFP_KERNEL);
> >
> > + local_irq_restore(flags);
> >
> > Clearly that's not going to work well at all.
>
> Furthermore there is a distinct lack of error handling there, it assumes
> the allocation always succeeds.
Yes, both of those issues are embarrassing. Thanks for pointing them
out. I'll take another swing at it.
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists