| To: | xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] [PATCH] [Xen] Check FADT's signature |
| From: | Stefan Berger <stefanb@xxxxxxxxxx> |
| Date: | 2007年8月09日 09:35:27 -0400 |
| Cc: | Keir Fraser <keir@xxxxxxxxxxxxx> |
| Delivery-date: | 2007年8月09日 06:24:57 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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>
Attachment:
fadt_check.diff
Description: Text Data
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [RFC] Suppress all use of ISA DMA on Xen , Jan Beulich |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] [Xen] Check FADT's signature , Keir Fraser |
| Previous by Thread: | [Xen-devel] [RFC] Suppress all use of ISA DMA on Xen , Jan Beulich |
| Next by Thread: | Re: [Xen-devel] [PATCH] [Xen] Check FADT's signature , Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |