Re: [git pull] d_revalidate pile

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

On Mon, Jan 27, 2025 at 05:32:18PM -0500, Sasha Levin wrote:
> [ Adding in the LKFT folks ]

Oops, sorry - didn't realise they weren't already on the report since it
was on LKFT or I'd have done the same.

> On Mon, Jan 27, 2025 at 08:38:50PM +0000, Mark Brown wrote:

> > have the ability to save the vmlinux.  Poking around the LKFT output it
> > does look like they're doing that for the LKFT builds:

> My understanding was that becuase CONFIG_DEBUG_INFO_NONE=y is set, we
> actually don't have enough info to resolve line numbers.

The arm64 and arm defconfigs which are the main ones I'd end up looking
at both set CONFIG_DEBUG_INFO (_REDUCED in the case of arm64), the trace
you posted was from arm64 so unless it was some config that overrode
things there ought to be info.  x86_64 which I guess you might use more
indeed doesn't have it.

> I've tried running decode_stacktrace.sh on the vmlinux image linked
> above, and indeed we can't get line numbers.

That was a random build I pulled out which turns out to be a tinyconfig
rather than the specific build that was used - if we look at an arm64
defconfig (your trace looked to be from arm64):

    https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.13-rc7-8584-gd4639f3659ae/testrun/27028517/suite/build/test/clang-nightly-defconfig-40bc7ee5/details/
    https://storage.tuxsuite.com/public/linaro/lkft/builds/2sDW1oYDQrsEOOs4L6yoysbu9aS/

I'm able to decode (just feeding a random log message in, no idea what
specific build generated the log message so the line number is almost
certainly wrong):

   $ echo [   62.184178]  d_same_name+0x4c/0xd0 | ./scripts/decode_stacktrace.sh /tmp/vmlinux
   [   62.184178] d_same_name (fs/dcache.c:2127)  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]