On Thu, Aug 18, 2022 at 01:53:06PM +0200, Alexander Lobakin wrote: > Currently, kallsyms kernel code copes with symbols with the same > name by indexing them according to their position in vmlinux and > requiring to provide an index of the desired symbol. This is not > really quite reliable and is fragile to any features performing > symbol or section manipulations such as FG-KASLR. Ah, here's the reasoning, stuff like this should go into the 0/X message too, right? Anyway, what is currently broken that requires this? What will this make easier in the future? What in the future will depend on this? > So, in order to make kallsyms immune to object code modification What do you mean by "object code modification"? Can that happen now? What causes it? What happens if it does happen? And why are any of these being cc:ed to the stable mailing list? confused, greg k-h
