Re: [PATCH linux-next] lockd: nlmclnt_reclaim(): avoid stack overflow

2013-02-14 Thread Jeff Layton
On Tue, 12 Feb 2013 12:33:15 -0700 Tim Gardner wrote: > Even though nlmclnt_reclaim() is only one call into the stack frame, > 928 bytes on the stack seems like a lot. Recode to dynamically > allocate the request structure once from within the reclaimer task, > then pass this pointer into nlmclnt

Re: [PATCH linux-next] lockd: nlmclnt_reclaim(): avoid stack overflow

2013-02-12 Thread J. Bruce Fields
On Tue, Feb 12, 2013 at 12:33:15PM -0700, Tim Gardner wrote: > Even though nlmclnt_reclaim() is only one call into the stack frame, > 928 bytes on the stack seems like a lot. Recode to dynamically > allocate the request structure once from within the reclaimer task, > then pass this pointer into nl

[PATCH linux-next] lockd: nlmclnt_reclaim(): avoid stack overflow

2013-02-12 Thread Tim Gardner
Even though nlmclnt_reclaim() is only one call into the stack frame, 928 bytes on the stack seems like a lot. Recode to dynamically allocate the request structure once from within the reclaimer task, then pass this pointer into nlmclnt_reclaim() for reuse on subsequent calls. smatch analysis: fs/