Hi, list,
I am a newbie for tboot. As you can easily imagine, I've got an issue that
kernel symbol tables seems to be changed when booting with tboot. For
example, the addresses of init_uts_ns are different between /proc/kallsyms
and my System.map file.
* System.map
# cat /boot/System.map-2.6.32-202.el6.i686 | grep -w init_uts_ns
c0a2f380 D init_uts_ns
* kallsyms
# cat /proc/kallsyms | grep -w init_uts_ns
c122f380 D init_uts_ns
The gap is 0x800000 and it looks to match up with ptab_base. I am using the
System.map file to develop a custom tool so that this change could be a
problem. Is there anyone who can verify if it is expected result? Any
comment would be helpful.
Thanks in advance,
Rogan Kyuseok Lee
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
tboot-devel mailing list
tboot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tboot-devel
