This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 3/3] PR4886: Check build-id in module_init function if able.


> I'm not sure when the build-id is updated, but interested in your
> enhancement. :-)
> If I'm using an out-of-tree driver, is build-id updated when I updated
> the driver's source code but didn't change running kernel?
> In other words, would each driver have its build-id which is different
> from other drivers and kernel?

Yes, every non-identical build of a .ko file should result in a distinct
build ID embedded in that .ko file.  Only if you rebuild the same code to
get the same binary should get you the same build ID.  (The build IDs of
the related kernel or of other .ko's have nothing to do with this.)


Thanks,
Roland


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]