Check the signature of the alleged FADT and only parse it if it really
is the FADT and not something else. I understand that this is not the
real solution, but prevents other bad things from happening, like the
timer going backwards if a bogus PM-Timer port is picked up.
Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
fadt_check.diff
Description: Text Data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|