lkml.org 
[lkml]   [2009]   [Oct]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH -tip perf/probes 00/10] x86 insn decoder bugfixes
Date
> Thirdly, i think we should expose the build-id of the kernel and the 
> path to the vmlinux (and modules) via /proc/build-id or so. That way
> tooling can find the vmlinux file and can validate that it matches the
> kernel's signature. (maybe include a file date as well - that's a faster
> check than a full build-id checksum, especially for large kernels)

You seem to be confused about what build IDs are. There is no "checksum
validation". Once the bits are stored there is no calculation ever done
again, only exact comparison with an expected build ID bitstring. The size
of an object file is immaterial.

As Frank mentioned, the kernel's and modules' allocated ELF notes (and thus
build IDs) are already exposed in /sys. Tools like "eu-unstrip -nk" use
this information today.


Thanks,
Roland


\
 
 \ /
  Last update: 2009-10-29 20:21    [from the cache]
©2003-2011 Jasper Spaans