diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2022-05-05 16:22:35 +0900 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2022-05-11 21:46:39 +0900 |
commit | 78e9e56af3858bf2c52c065daa6c8bee0d72048c (patch) | |
tree | 77732a7f52cdd495fae4ef92a1fce5efd326b913 /scripts/mod/modpost.h | |
parent | e493f472752000968f5b30aac10391288cfbf5b1 (diff) | |
download | linux-78e9e56af3858bf2c52c065daa6c8bee0d72048c.tar.bz2 |
kbuild: record symbol versions in *.cmd files
When CONFIG_MODVERSIONS=y, the output from genksyms is saved in
separate *.symversions files, and will be used much later when
CONFIG_LTO_CLANG=y because it is impossible to update LLVM bit code
here.
This approach is not robust because:
- *.symversions may or may not exist. If *.symversions does not
exist, we never know if it is missing for legitimate reason
(i.e. no EXPORT_SYMBOL) or something bad has happened (for
example, the user accidentally deleted it). Once it occurs,
it is not self-healing because *.symversions is generated
as a side effect.
- stale (i.e. invalid) *.symversions might be picked up if an
object is generated in a non-ordinary way, and corresponding
*.symversions (, which was generated by old builds) just happen
to exist.
A more robust approach is to save symbol versions in *.cmd files
because:
- *.cmd always exists (if the object is generated by if_changed
rule or friends). Even if the user accidentally deletes it,
it will be regenerated in the next build.
- *.cmd is always re-generated when the object is updated. This
avoid stale version information being picked up.
I will remove *.symversions later.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Tested-by: Nicolas Schier <nicolas@fjasle.eu>
Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
Tested-by: Nathan Chancellor <nathan@kernel.org>
Diffstat (limited to 'scripts/mod/modpost.h')
0 files changed, 0 insertions, 0 deletions