Mike Rapoport d9655c6854 Revert "x86/setup: don't remove E820_TYPE_RAM for pfn 0"
commit 5c279c4cf206e03995e04fd3404fa95ffd243a97 upstream.

This reverts commit bde9cfa3afe4324ec251e4af80ebf9b7afaf7afe.

Changing the first memory page type from E820_TYPE_RESERVED to
E820_TYPE_RAM makes it a part of "System RAM" resource rather than a
reserved resource and this in turn causes devmem_is_allowed() to treat
is as area that can be accessed but it is filled with zeroes instead of
the actual data as previously.

The change in /dev/mem output causes lilo to fail as was reported at
slakware users forum, and probably other legacy applications will
experience similar problems.

Link: https://www.linuxquestions.org/questions/slackware-14/slackware-current-lilo-vesa-warnings-after-recent-updates-4175689617/#post6214439
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-02-07 15:37:13 +01:00
..
2020-03-30 19:14:28 -07:00
2020-06-11 15:15:23 +02:00
2020-02-26 15:21:22 +01:00
2019-11-12 16:21:15 +01:00
2019-11-12 16:21:15 +01:00
2020-10-23 11:17:56 -07:00
2020-09-10 10:43:13 -05:00
2020-06-02 10:59:12 -07:00
2020-09-01 09:58:06 +02:00
2020-08-20 13:12:58 +02:00
2020-03-21 16:03:25 +01:00
2020-06-11 15:54:31 -07:00
2020-07-27 14:31:07 -04:00
2020-07-27 14:31:07 -04:00
2020-02-16 20:58:06 +01:00
2020-09-10 11:19:29 +02:00
2020-08-04 14:47:45 -07:00