Re: [PATCH v5 3/4] scripts: add verifier script for builtin module range data

[Kris Van Hees <kris.van.hees@oracle.com>]

On Wed, Aug 14, 2024 at 04:16:06PM -0400, Steven Rostedt wrote:
> On Wed, 14 Aug 2024 15:59:58 -0400
> Kris Van Hees <kris.van.hees@oracle.com> wrote:
> 
> > > What does this mean?  
> > 
> > Hm, this is certainly why the validation script exists.  I am surprised, though
> > not entirely because kernel changes toward the 6.10 branching and such came
> > after I create this version.  Would you be willing to send me a copy of your
> > .config for this kernel build so I can investigate?  This output is typical
> > of a case where the script was not able to determine offse ranges correctly.
> 
> Attached.

So, looking back at your output it seems that the problem is that I did not
make it obvious that the verifier script is written to be executed from the
root of the kernel build tree, i.e. where the objects are stored.  I'll add
support for an optional extra argument to the script so that a path to the
actual object tree can be provided.  That was an important oversight on my
part - sorry about that.

So, if your kernel is built into an object directory, the script in its
current state would need to be executed with that object directory as current
working directory.

I.e. if the build directory is /work/build/nobackup/debiantesting-x86-64/ and
the kernel source tree is in /work/source/linux, change CWD to that build
directory and invoke the verifier as:

/work/source/linux/scripts/verify_builtin_ranges.awk modules.builtin.ranges System.map modules.builtin vmlinux.map vmlinux.o.map

Can you try that and verify that the output is correct in that case?  I expect
it will be.

v6 of the series (which I hope to post tomorrow) will allow you to specify
the path to the object tree so that this will be more user friendly.

	Kris