Re: [PATCH resend] fs/proc: Move kfree outside pde_unload_lock

[Nathan Zimmer]

On 04/08/2013 10:58 AM, Al Viro wrote:
> On Mon, Apr 08, 2013 at 10:34:07AM -0500, Nathan Zimmer wrote:
> > On 04/05/2013 04:00 PM, Al Viro wrote:
> > > On Fri, Apr 05, 2013 at 03:56:17PM -0500, Nathan Zimmer wrote:
> > >
> > > > That didn't produce anything.  I'll run some bisections over the
> > > > weekend and see what I can sort out.
> > > *Ugh*
> > >
> > > I'd try to build with DEBUG_KMEMLEAK and slapped printks on the entry
> > > and exit from close_pdeo().  If that doesn't show anything interesting,
> > > it's probably unrelated to procfs...
> > My bisection pointed me to this commit:  e41efbf13c15
> > At this point I am assuming my issue is unrelated to procfs.
> Huh?  That commit simply moves three functions and one struct from one file to
> another...

Further digging seems to indicate 9984d7394618df9, the one right after 
the commit I previously identified.
Not sure what I did wrong with my bisect to put it off by one.


--
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/