diff options
| author | Don Zickus <dzickus@redhat.com> | 2011-02-07 23:25:00 -0500 |
|---|---|---|
| committer | Willy Tarreau <w@1wt.eu> | 2011-04-30 16:53:10 +0200 |
| commit | b027411d8a248441e116828209cab3493d1a4957 (patch) | |
| tree | 117df1f2e5aeb03eb9256d05cae43daac98ce78f /crypto/aead.c | |
| parent | b682df61246f730b1d4699a6e9c8a5351e681a7d (diff) | |
x86: Use u32 instead of long to set reset vector back to 0
commit 299c56966a72b9109d47c71a6db52097098703dd upstream.
A customer of ours, complained that when setting the reset
vector back to 0, it trashed other data and hung their box.
They noticed when only 4 bytes were set to 0 instead of 8,
everything worked correctly.
Mathew pointed out:
|
| We're supposed to be resetting trampoline_phys_low and
| trampoline_phys_high here, which are two 16-bit values.
| Writing 64 bits is definitely going to overwrite space
| that we're not supposed to be touching.
|
So limit the area modified to u32.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Acked-by: Matthew Garrett <mjg@redhat.com>
LKML-Reference: <1297139100-424-1-git-send-email-dzickus@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'crypto/aead.c')
0 files changed, 0 insertions, 0 deletions