On Nov 7, 2006, at 10:14 AM, Christos Zoulas wrote:

> It is just telling you it will not be able to stack-protect those
> functions.

Ok, rather than adding a warning flag that applies to the entire file,  
I'd much rather see a new function attribute --  
__attribute__((__no_stack_protect__)) perhaps? -- so that we can  
pinpoint which functions we want to suppress the warning on.

Yes, this means compiler work, but I think it's a better solution  
overall.  I don't think it's a great idea to mandate "no alloca() or  
variable array allocations in the kernel", especially if we have a  
long-term goal of providing ABI stability in the kernel.

-- thorpej