linux-kernel - Aw: Re: [External] : nfsd: memory leak when client does many file operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <trinity-db4c718f-d59d-4de4-bf45-96ad98ca2362-1711471819632@msvc-mesg-gmx122>
Date: Tue, 26 Mar 2024 17:50:19 +0100
From: Jan Schunk <scpcom@....de>
To: Chuck Lever III <chuck.lever@...cle.com>
Cc: Jeff Layton <jlayton@...nel.org>, Neil Brown <neilb@...e.de>, Olga
 Kornievskaia <kolga@...app.com>, Dai Ngo <dai.ngo@...cle.com>, Tom Talpey
 <tom@...pey.com>, Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Aw: Re: [External] : nfsd: memory leak when client does many file
 operations

Thanks, I do some tests with DEBUG_KMEMLEAK enabled and git bisect now.

> Gesendet: Montag, den 25.03.2024 um 21:36 Uhr
> Von: "Chuck Lever III" <chuck.lever@...cle.com>
> An: "Jan Schunk" <scpcom@....de>
> Cc: "Jeff Layton" <jlayton@...nel.org>, "Neil Brown" <neilb@...e.de>, "Olga Kornievskaia" <kolga@...app.com>, "Dai Ngo" <dai.ngo@...cle.com>, "Tom Talpey" <tom@...pey.com>, "Linux NFS Mailing List" <linux-nfs@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
> Betreff: Re: [External] : nfsd: memory leak when client does many file operations
> 
> 
> 
> > On Mar 25, 2024, at 4:26 PM, Jan Schunk <scpcom@....de> wrote:
> > 
> > I am building my own kernels, but I never tried kmemleak, is this just a Kconfig option?
> 
>   Location:
>     -> Kernel hacking
>       -> Memory Debugging
> (1)     -> Kernel memory leak detector (DEBUG_KMEMLEAK [=n])
> 
> 
> > What do you mean with "bisect between v6.3 and v6.4"?
> 
> After you "git clone" the kernel source:
> 
> $ git bisect start v6.4 v6.3
> 
> Build the kernel and test. If the test fails:
> 
> $ cd <your kernel source tree>; git bisect bad
> 
> If the test succeeds:
> 
> $ cd <your kernel source tree>; git bisect good
> 
> Rebuild and try again until it lands on the first broken commit.
> 
> 
> > Everything including v6.4 is OK, the problem starts at v6.5.
> 
> I misremembered. Use "$ git bisect start v6.5 v6.4" then.
> 
> 
> > I also looked at some code already but there are huge changes to mm that happened in v6.5 and v6.6 so for me it is heavy to compare it with older versions to find one or more commits that may cause the issue.
> 
> Bisection is a mechanical test-based process. You don't need
> to look at code until you've reached the first bad commit.
> 
> --
> Chuck Lever
> 
>