diff options
| author | Don Zickus <dzickus@redhat.com> | 2011-02-08 07:25:00 +0300 |
|---|---|---|
| committer | Paul Gortmaker <paul.gortmaker@windriver.com> | 2011-06-26 20:46:53 +0400 |
| commit | d333643bbe0d7a0634bc988ae379f8fa602df2f7 (patch) | |
| tree | 70f2f4487ca5b2f4d42c7abacf2667b057b025be /fs/fuse/fuse_i.h | |
| parent | 98fc9c1d3390e780292bd877c77ebf31a1a879d7 (diff) | |
| download | linux-d333643bbe0d7a0634bc988ae379f8fa602df2f7.tar.xz | |
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: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'fs/fuse/fuse_i.h')
0 files changed, 0 insertions, 0 deletions