lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHP4M8Vj-BmDXQgF-rkLr5fthey7RVaZ-1o87yTUg=9uh4hEOw@mail.gmail.com>
Date:   Sat, 22 Jun 2019 20:58:29 +0530
From:   Ajay Garg <ajaygargnsit@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Difference in values of addresses in System.map and /proc/kallsyms

Hi All.

My system is

ajay@...itude-3480:~$ uname -a
Linux latitude-3480 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar
14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


When I see the address for a symbol, say linux_banner, in
/boot/System.map-4.13.0-38-generic, it shows
ffffffff81e00120 R linux_banner

However, when I see it in /proc/kallsyms, it shows
ffffffffa7000120 R linux_banner


Also, I note that /proc/kallsyms addresses vary upon reboots, so I am
a little confused as to what the entries in /proc/kallsyms really
mean.
So, will be grateful for some pointers from the experts :)


Thanks and Regards,
Ajay

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ