diff options
| author | Daniel Drake <dsd@laptop.org> | 2013-08-09 18:14:20 -0400 |
|---|---|---|
| committer | H. Peter Anvin <hpa@linux.intel.com> | 2013-08-09 15:29:48 -0700 |
| commit | d55e37bb0f51316e552376ddc0a3fff34ca7108b (patch) | |
| tree | aa463bff9b5f8c5933f6b7c82c06b39243dbbf3c /fs/lockd/clntlock.c | |
| parent | 58c59bc997d86593f0bea41845885917cf304d22 (diff) | |
| download | linux-next-d55e37bb0f51316e552376ddc0a3fff34ca7108b.tar.gz | |
x86: Don't clear olpc_ofw_header when sentinel is detected
OpenFirmware wasn't quite following the protocol described in boot.txt
and the kernel has detected this through use of the sentinel value
in boot_params. OFW does zero out almost all of the stuff that it should
do, but not the sentinel.
This causes the kernel to clear olpc_ofw_header, which breaks x86 OLPC
support.
OpenFirmware has now been fixed. However, it would be nice if we could
maintain Linux compatibility with old firmware versions. To do that, we just
have to avoid zeroing out olpc_ofw_header.
OFW does not write to any other parts of the header that are being zapped
by the sentinel-detection code, and all users of olpc_ofw_header are
somewhat protected through checking for the OLPC_OFW_SIG magic value
before using it. So this should not cause any problems for anyone.
Signed-off-by: Daniel Drake <dsd@laptop.org>
Link: http://lkml.kernel.org/r/20130809221420.618E6FAB03@dev.laptop.org
Acked-by: Yinghai Lu <yinghai@kernel.org>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: <stable@vger.kernel.org> # v3.9+
Diffstat (limited to 'fs/lockd/clntlock.c')
0 files changed, 0 insertions, 0 deletions