From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Zimmer Subject: Re: [PATCH resend] fs/proc: Move kfree outside pde_unload_lock Date: Mon, 8 Apr 2013 10:34:07 -0500 Message-ID: <5162E36F.5020305@sgi.com> References: <515D9F8A.2060505@sgi.com> <1365090819-25448-1-git-send-email-nzimmer@sgi.com> <20130404161140.GR21522@ZenIV.linux.org.uk> <515DB465.1060004@sgi.com> <20130404204459.GU21522@ZenIV.linux.org.uk> <515F0456.9040803@sgi.com> <20130405173623.GE4068@ZenIV.linux.org.uk> <515F3A71.9080008@sgi.com> <20130405210042.GH4068@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , , "Eric W. Biederman" , David Woodhouse , To: Al Viro Return-path: In-Reply-To: <20130405210042.GH4068@ZenIV.linux.org.uk> Sender: stable-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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.