> On Mar 25, 2024, at 4:26 PM, Jan Schunk <scpcom@xxxxxx> 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
