Re: hunting memory corruption bug in 6.18.x

[Rik van Riel]

On Thu, 2026-10-01 at 21:40 +0200, Nikola Ciprich wrote:
> 
> Oops:
> general protection fault, probably for non-canonical address
> 0xfffffff0c930038
> RIP: __d_lookup+0x4a/0xc0
> Comm: systemd PID: 1274600 CPU: 23
> Call trace:
> __d_lookup
> lookup_fast
> walk_component
> link_path_walk
> path_openat

That is the exact same memory address as the
crash in your original report.

Do you capture any crashes with other memory
addresses, or do they always crash with this
same address?

If it's always the same address, we may not
be looking at random corruption at all, but
instead at some bug that results in the same
bad address every time.

That might narrow the problem space a little.

-- 
All Rights Reversed.