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

2024-08-14 Thread Kris Van Hees
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 wrote: > > > > What does this mean? > > > > Hm, this is certainly why the validation script exists. I am surprised, > > though > > not entirely because kernel changes toward t

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

2024-08-14 Thread Kris Van Hees
On Wed, Aug 14, 2024 at 03:19:45PM -0400, Steven Rostedt wrote: > > Hmm, does this handle my concern from the last patch. That is, if the > previous script is broken by some change, this will catch it? > If so, should there be a way to run this always? As it looks to be only > used for manual test

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

2024-08-14 Thread Steven Rostedt
Hmm, does this handle my concern from the last patch. That is, if the previous script is broken by some change, this will catch it? If so, should there be a way to run this always? As it looks to be only used for manual tests. On Mon, 15 Jul 2024 23:10:44 -0400 Kris Van Hees wrote: > The modul

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

2024-07-15 Thread Kris Van Hees
The modules.builtin.ranges offset range data for builtin modules is generated at compile time based on the list of built-in modules and the vmlinux.map and vmlinux.o.map linker maps. This data can be used to determine whether a symbol at a particular address belongs to module code that was configu