diff options
author | Kairui Song <kasong@redhat.com> | 2019-03-08 11:05:08 +0800 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2019-03-23 12:11:49 +0100 |
commit | ffc8599aa9763f39f6736a79da4d1575e7006f9a (patch) | |
tree | 564374b91fdfced43fbcbf2310cb05e3ca9759a4 /Documentation/hid/uhid.txt | |
parent | f7798711adeebde3c59ddd797a3f2da36c1005be (diff) | |
download | linux-ffc8599aa9763f39f6736a79da4d1575e7006f9a.tar.bz2 |
x86/gart: Exclude GART aperture from kcore
On machines where the GART aperture is mapped over physical RAM,
/proc/kcore contains the GART aperture range. Accessing the GART range via
/proc/kcore results in a kernel crash.
vmcore used to have the same issue, until it was fixed with commit
2a3e83c6f96c ("x86/gart: Exclude GART aperture from vmcore")', leveraging
existing hook infrastructure in vmcore to let /proc/vmcore return zeroes
when attempting to read the aperture region, and so it won't read from the
actual memory.
Apply the same workaround for kcore. First implement the same hook
infrastructure for kcore, then reuse the hook functions introduced in the
previous vmcore fix. Just with some minor adjustment, rename some functions
for more general usage, and simplify the hook infrastructure a bit as there
is no module usage yet.
Suggested-by: Baoquan He <bhe@redhat.com>
Signed-off-by: Kairui Song <kasong@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Jiri Bohac <jbohac@suse.cz>
Acked-by: Baoquan He <bhe@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Omar Sandoval <osandov@fb.com>
Cc: Dave Young <dyoung@redhat.com>
Link: https://lkml.kernel.org/r/20190308030508.13548-1-kasong@redhat.com
Diffstat (limited to 'Documentation/hid/uhid.txt')
0 files changed, 0 insertions, 0 deletions