Re: [PATCH 4/4] bootlinux: add support for A/B kernel testing

[Chuck Lever <cel@kernel.org>]

On 7/26/25 6:46 PM, Luis Chamberlain wrote:
> On Sat, Jul 26, 2025 at 01:21:16PM -0700, Luis Chamberlain wrote:
>> Maybe we should enable CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC and 
>> to enhance this further perhaps we can also add either upstream to Linux
>> or on kdevops an equivalent sha256sum of the config. So if not upstream
>> on Linux we'd add to the kdevops kconfig cat linux/.config | sha256sum
>> and I'd hope that $(zcat /proc/config.gz | sha256sum) on the runtime on
>> the booted target DUT would match.
> 
> Actually, augmenting the upstream way to append the version to *also*
> append a checksum of the kernel config would be even more deterministic.
> But this is getting out of hand in terms of how long that string would
> get. I wonder if a) do we care about that long lenght b) if we should
> have more information just printed on the kernel boot like this
> metadata. Then uname -c or something could be added to, to help us get
> the config checksum used.
Well, we are basically looking for a way to identify which release is
under test (or which RPM should be installed). Maybe the 12-hexit hash
plus the build date is unique enough?


-- 
Chuck Lever