From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH] vsprintf.c: Use noinline_for_stack Date: Sat, 13 Mar 2010 09:44:55 -0800 Message-ID: <1268502295.30289.44.camel@Joe-Laptop.home> References: <20100304143837.af39845d.akpm@linux-foundation.org> <1267911399.849.39.camel@Joe-Laptop.home> <1267914654.849.81.camel@Joe-Laptop.home> <1267918554.849.89.camel@Joe-Laptop.home> <1267924214.1937.12.camel@Joe-Laptop.home> <1267929215.1937.18.camel@Joe-Laptop.home> <20100312162559.a8e51777.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Nick Andrew , Linux Kernel Mailing List , Greg Kroah-Hartman , netdev@vger.kernel.org, Bjorn Helgaas To: Linus Torvalds Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Sat, 2010-03-13 at 07:35 -0800, Linus Torvalds wrote: > On Fri, 12 Mar 2010, Andrew Morton wrote: > > nice. > But the kallsyms_lookup()/sprint_symbol() functions don't take a > length parameter, so we have to do the worst-case thing (which itself has > tons of unnecessary padding). I sent a patch once about that using a struct because I didn't like the unbounded sprint http://lkml.org/lkml/2009/4/15/16 > Gaah. We do _not_ want a kmalloc() or something like that in this path, > since its' very much used for oopses (which in turn may be due to various > slab bugs etc). Perhaps a new snprint_symbol function with the other kallsyms... functions changed as necessary. thoughts?