x86/gart/kcore: Exclude GART aperture from kcore
Subsystems (3)
PATCH v5 1/1 x86/gart/kcore: Exclude GART aperture from kcore
On machines where the GART aperture is mapped over physical RAM, /proc/kcore contains the GART aperture range and reading it may lead to kernel panic.
Vmcore used to have the same issue, until we fixed it in 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.
We apply the same workaround for kcore. First implement the same hook infrastructure for kcore, then reuse the hook functions introduced in 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.
---
Update from V4:
- Remove the unregistering funtion and move functions never used after init to .init
Update from V3:
- Reuse the approach in V2, as Jiri noticed V3 approach may fail some use case. It introduce overlapped region in kcore, and can't garenteen the read request will fall into the region we wanted.
- Improve some function naming suggested by Baoquan in V2.
- Simplify the hook registering and checking, we are not exporting the hook register function for now, no need to make it that complex.
Update from V2:
Instead of repeating the same hook infrastructure for kcore, introduce a new kcore area type to avoid reading from, and let kcore always bypass this kind of area.
Update from V1:
Fix a complie error when CONFIG_PROC_KCORE is not set
arch/x86/kernel/aperture_64.c | 20 +++++++++++++------- fs/proc/kcore.c | 27 +++++++++++++++++++++++++++ include/linux/kcore.h | 2 ++ 3 files changed, 42 insertions(+), 7 deletions(-)
arch/x86/kernel/aperture_64.c +13 -7
@@ -14,6 +14,7 @@#define pr_fmt (fmt) "AGP: " fmt#include <linux/kernel.h> +#include <linux/kcore.h> #include <linux/types.h> #include <linux/init.h> #include <linux/memblock.h>
@@ -57,7 +58,7 @@ int fallback_aper_force __initdata;int fix_aperture__initdata =1 ; -#ifdef CONFIG_PROC_VMCORE +#if defined(CONFIG_PROC_VMCORE ) || defined(CONFIG_PROC_KCORE )/* * If the first kernel maps the aperture over e820 RAM, the kdump kernel will * use the same range because it will remain configured in the northbridge.
@@ -66,20 +67,25 @@ int fix_aperture __initdata = 1;*/ static unsigned long aperture_pfn_start, aperture_page_count; -static int gart_oldmem_pfn_is_ram (unsigned long pfn) +static int gart_mem_pfn_is_ram (unsigned long pfn) {return likely ((pfn < aperture_pfn_start) || (pfn >= aperture_pfn_start + aperture_page_count)); } -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void __init exclude_from_core (u64 aper_base,u32 aper_order) { aperture_pfn_start = aper_base >>PAGE_SHIFT ; aperture_page_count = (32 *1024 *1024 ) << aper_order >>PAGE_SHIFT ; -WARN_ON (register_oldmem_pfn_is_ram (&gart_oldmem_pfn_is_ram)); +#ifdef CONFIG_PROC_VMCORE +WARN_ON (register_oldmem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif +#ifdef CONFIG_PROC_KCORE +WARN_ON (register_mem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif }#else -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void exclude_from_core (u64 aper_base,u32 aper_order) { }#endif
@@ -474,7 +480,7 @@ int __init gart_iommu_hole_init(void)* may have allocated the range over its e820 RAM * and fixed up the northbridge */ -exclude_from_vmcore (last_aper_base, last_aper_order); +exclude_from_core (last_aper_base, last_aper_order);return 1 ; }
@@ -520,7 +526,7 @@ int __init gart_iommu_hole_init(void)* overlap with the first kernel's memory. We can't access the * range through vmcore even though it should be part of the dump. */ -exclude_from_vmcore (aper_alloc, aper_order); +exclude_from_core (aper_alloc, aper_order);/* Fix up the north bridges */ for (i =0 ; i < amd_nb_bus_dev_ranges[i].dev_limit; i++) {
fs/proc/kcore.c +27 -0
@@ -54,6 +54,28 @@ static LIST_HEAD(kclist_head);static DECLARE_RWSEM (kclist_lock);static int kcore_need_update =1 ; +/* +* Returns > 0 for RAM pages, 0 for non-RAM pages, < 0 on error +* Same as oldmem_pfn_is_ram in vmcore +*/ +static int (*mem_pfn_is_ram)(unsigned long pfn); + +int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn)) +{ +if (mem_pfn_is_ram) +return -EBUSY ; + mem_pfn_is_ram = fn; +return 0 ; +} + +static int pfn_is_ram (unsigned long pfn) +{ +if (mem_pfn_is_ram) +return mem_pfn_is_ram (pfn); +else +return 1 ; +} +/* This doesn't grab kclist_lock, so it should only be used at init time. */ void __init kclist_add (struct kcore_list *new,void *addr,size_t size,int type)
@@ -465,6 +487,11 @@ read_kcore(struct file *file, char __user *buffer, size_t buflen, loff_t *fpos) goto out; } m =NULL ;/* skip the list anchor */ + }else if (!pfn_is_ram (__pa (start) >>PAGE_SHIFT )) { +if (clear_user (buffer, tsz)) { + ret = -EFAULT ; + goto out; + } }else if (m->type ==KCORE_VMALLOC ) {vread (buf, (char *)start, tsz);/* we have to zero-fill user buffer even if no read */
include/linux/kcore.h +2 -0
@@ -44,6 +44,8 @@ void kclist_add_remap(struct kcore_list *m, void *addr, void *vaddr, size_t sz) m->vaddr = (unsigned long )vaddr; kclist_add(m, addr, sz, KCORE_REMAP); } + +extern int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn));#else static inline void kclist_add (struct kcore_list *new,void *addr,size_t size,int type)
Signature · 1 line
2.20.1
Quoted 2 lines · Kairui Song
Suggested-by Baoquan He <[email protected]>Signed-off-by Kairui Song <[email protected]>
Thanks,
Signature · 2 lines
Jiri Bohac <[email protected]> SUSE Labs, Prague, Czechia
Quoted 16 lines · Kairui Song
On machines where the GART aperture is mapped over physical RAM,
/proc/kcorecontains the GART aperture range and reading it may lead to kernel panic.Vmcore used to have the same issue, until we fixed it in commit
2a3e83c6f96c("x86/gart: Exclude GART aperture from vmcore")', leveraging existing hook infrastructure in vmcore to let/proc/vmcorereturn zeroes when attempting to read the aperture region, and so it won't read from the actual memory.We apply the same workaround for kcore. First implement the same hook infrastructure for kcore, then reuse the hook functions introduced in 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.
Quoted 5 lines
Suggested-by Baoquan He <[email protected]>Signed-off-by Kairui Song <[email protected]>---
Looks good to me, thanks for the effort.
Thanks
Baoquan
Quoted 155 lines
Update from V4:
- Remove the unregistering funtion and move functions never used after init to .initUpdate from V3:
- Reuse the approach in V2, as Jiri noticed V3 approach may fail some use case. It introduce overlapped region in kcore, and can't garenteen the read request will fall into the region we wanted.
- Improve some function naming suggested by Baoquan in V2.
- Simplify the hook registering and checking, we are not exporting the hook register function for now, no need to make it that complex.Update from V2:
Instead of repeating the same hook infrastructure for kcore, introduce a new kcore area type to avoid reading from, and let kcore always bypass this kind of area.Update from V1:
Fix a complie error whenCONFIG_PROC_KCOREis not setarch/x86/kernel/aperture_64.c | 20 +++++++++++++------- fs/proc/kcore.c | 27 +++++++++++++++++++++++++++ include/linux/kcore.h | 2 ++ 3 files changed, 42 insertions(+), 7 deletions(-)arch/x86/kernel/aperture_64.c +13
-7@@ -14,6 +14,7 @@#define pr_fmt (fmt) "AGP: " fmt#include <linux/kernel.h> +#include <linux/kcore.h> #include <linux/types.h> #include <linux/init.h> #include <linux/memblock.h> @@ -57,7 +58,7 @@ int fallback_aper_force __initdata;int fix_aperture__initdata =1 ; -#ifdef CONFIG_PROC_VMCORE +#if defined(CONFIG_PROC_VMCORE ) || defined(CONFIG_PROC_KCORE )/* * If the first kernel maps the aperture over e820 RAM, the kdump kernel will * use the same range because it will remain configured in the northbridge. @@ -66,20 +67,25 @@ int fix_aperture __initdata = 1;*/ static unsigned long aperture_pfn_start, aperture_page_count; -static int gart_oldmem_pfn_is_ram (unsigned long pfn) +static int gart_mem_pfn_is_ram (unsigned long pfn) {return likely ((pfn < aperture_pfn_start) || (pfn >= aperture_pfn_start + aperture_page_count)); } -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void __init exclude_from_core (u64 aper_base,u32 aper_order) { aperture_pfn_start = aper_base >>PAGE_SHIFT ; aperture_page_count = (32 *1024 *1024 ) << aper_order >>PAGE_SHIFT ; -WARN_ON (register_oldmem_pfn_is_ram (&gart_oldmem_pfn_is_ram)); +#ifdef CONFIG_PROC_VMCORE +WARN_ON (register_oldmem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif +#ifdef CONFIG_PROC_KCORE +WARN_ON (register_mem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif }#else -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void exclude_from_core (u64 aper_base,u32 aper_order) { }#endif @@ -474,7 +480,7 @@ int __init gart_iommu_hole_init(void)* may have allocated the range over its e820 RAM * and fixed up the northbridge */ -exclude_from_vmcore (last_aper_base, last_aper_order); +exclude_from_core (last_aper_base, last_aper_order);return 1 ; }@@ -520,7 +526,7 @@ int __init gart_iommu_hole_init(void)* overlap with the first kernel's memory. We can't access the * range through vmcore even though it should be part of the dump. */ -exclude_from_vmcore (aper_alloc, aper_order); +exclude_from_core (aper_alloc, aper_order);/* Fix up the north bridges */ for (i =0 ; i < amd_nb_bus_dev_ranges[i].dev_limit; i++) {fs/proc/kcore.c +27
-0@@ -54,6 +54,28 @@ static LIST_HEAD(kclist_head);static DECLARE_RWSEM (kclist_lock);static int kcore_need_update =1 ; +/* +* Returns > 0 for RAM pages, 0 for non-RAM pages, < 0 on error +* Same as oldmem_pfn_is_ram in vmcore +*/ +static int (*mem_pfn_is_ram)(unsigned long pfn); + +int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn)) +{ +if (mem_pfn_is_ram) +return -EBUSY ; + mem_pfn_is_ram = fn; +return 0 ; +} + +static int pfn_is_ram (unsigned long pfn) +{ +if (mem_pfn_is_ram) +return mem_pfn_is_ram (pfn); +else +return 1 ; +} +/* This doesn't grab kclist_lock, so it should only be used at init time. */ void __init kclist_add (struct kcore_list *new,void *addr,size_t size,int type)@@ -465,6 +487,11 @@ read_kcore(struct file *file, char __user *buffer, size_t buflen, loff_t *fpos) goto out; } m =NULL ;/* skip the list anchor */ + }else if (!pfn_is_ram (__pa (start) >>PAGE_SHIFT )) { +if (clear_user (buffer, tsz)) { + ret = -EFAULT ; + goto out; + } }else if (m->type ==KCORE_VMALLOC ) {vread (buf, (char *)start, tsz);/* we have to zero-fill user buffer even if no read */ include/linux/kcore.h +2
-0@@ -44,6 +44,8 @@ void kclist_add_remap(struct kcore_list *m, void *addr, void *vaddr, size_t sz) m->vaddr = (unsigned long )vaddr; kclist_add(m, addr, sz, KCORE_REMAP); } + +extern int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn));#else static inline void kclist_add (struct kcore_list *new,void *addr,size_t size,int type)Signature · 1 line
2.20.1
Quoted 175 lines · Kairui Song
On machines where the GART aperture is mapped over physical RAM,
/proc/kcorecontains the GART aperture range and reading it may lead to kernel panic.Vmcore used to have the same issue, until we fixed it in commit
2a3e83c6f96c("x86/gart: Exclude GART aperture from vmcore")', leveraging existing hook infrastructure in vmcore to let/proc/vmcorereturn zeroes when attempting to read the aperture region, and so it won't read from the actual memory.We apply the same workaround for kcore. First implement the same hook infrastructure for kcore, then reuse the hook functions introduced in 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 <[email protected]>Signed-off-by Kairui Song <[email protected]>---
Update from V4:
- Remove the unregistering funtion and move functions never used after init to .initUpdate from V3:
- Reuse the approach in V2, as Jiri noticed V3 approach may fail some use case. It introduce overlapped region in kcore, and can't garenteen the read request will fall into the region we wanted.
- Improve some function naming suggested by Baoquan in V2.
- Simplify the hook registering and checking, we are not exporting the hook register function for now, no need to make it that complex.Update from V2:
Instead of repeating the same hook infrastructure for kcore, introduce a new kcore area type to avoid reading from, and let kcore always bypass this kind of area.Update from V1:
Fix a complie error whenCONFIG_PROC_KCOREis not setarch/x86/kernel/aperture_64.c | 20 +++++++++++++------- fs/proc/kcore.c | 27 +++++++++++++++++++++++++++ include/linux/kcore.h | 2 ++ 3 files changed, 42 insertions(+), 7 deletions(-)arch/x86/kernel/aperture_64.c +13
-7@@ -14,6 +14,7 @@#define pr_fmt (fmt) "AGP: " fmt#include <linux/kernel.h> +#include <linux/kcore.h> #include <linux/types.h> #include <linux/init.h> #include <linux/memblock.h> @@ -57,7 +58,7 @@ int fallback_aper_force __initdata;int fix_aperture__initdata =1 ; -#ifdef CONFIG_PROC_VMCORE +#if defined(CONFIG_PROC_VMCORE ) || defined(CONFIG_PROC_KCORE )/* * If the first kernel maps the aperture over e820 RAM, the kdump kernel will * use the same range because it will remain configured in the northbridge. @@ -66,20 +67,25 @@ int fix_aperture __initdata = 1;*/ static unsigned long aperture_pfn_start, aperture_page_count; -static int gart_oldmem_pfn_is_ram (unsigned long pfn) +static int gart_mem_pfn_is_ram (unsigned long pfn) {return likely ((pfn < aperture_pfn_start) || (pfn >= aperture_pfn_start + aperture_page_count)); } -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void __init exclude_from_core (u64 aper_base,u32 aper_order) { aperture_pfn_start = aper_base >>PAGE_SHIFT ; aperture_page_count = (32 *1024 *1024 ) << aper_order >>PAGE_SHIFT ; -WARN_ON (register_oldmem_pfn_is_ram (&gart_oldmem_pfn_is_ram)); +#ifdef CONFIG_PROC_VMCORE +WARN_ON (register_oldmem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif +#ifdef CONFIG_PROC_KCORE +WARN_ON (register_mem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif }#else -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void exclude_from_core (u64 aper_base,u32 aper_order) { }#endif @@ -474,7 +480,7 @@ int __init gart_iommu_hole_init(void)* may have allocated the range over its e820 RAM * and fixed up the northbridge */ -exclude_from_vmcore (last_aper_base, last_aper_order); +exclude_from_core (last_aper_base, last_aper_order);return 1 ; }@@ -520,7 +526,7 @@ int __init gart_iommu_hole_init(void)* overlap with the first kernel's memory. We can't access the * range through vmcore even though it should be part of the dump. */ -exclude_from_vmcore (aper_alloc, aper_order); +exclude_from_core (aper_alloc, aper_order);/* Fix up the north bridges */ for (i =0 ; i < amd_nb_bus_dev_ranges[i].dev_limit; i++) {fs/proc/kcore.c +27
-0@@ -54,6 +54,28 @@ static LIST_HEAD(kclist_head);static DECLARE_RWSEM (kclist_lock);static int kcore_need_update =1 ; +/* +* Returns > 0 for RAM pages, 0 for non-RAM pages, < 0 on error +* Same as oldmem_pfn_is_ram in vmcore +*/ +static int (*mem_pfn_is_ram)(unsigned long pfn); + +int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn)) +{ +if (mem_pfn_is_ram) +return -EBUSY ; + mem_pfn_is_ram = fn; +return 0 ; +} + +static int pfn_is_ram (unsigned long pfn) +{ +if (mem_pfn_is_ram) +return mem_pfn_is_ram (pfn); +else +return 1 ; +} +/* This doesn't grab kclist_lock, so it should only be used at init time. */ void __init kclist_add (struct kcore_list *new,void *addr,size_t size,int type)@@ -465,6 +487,11 @@ read_kcore(struct file *file, char __user *buffer, size_t buflen, loff_t *fpos) goto out; } m =NULL ;/* skip the list anchor */ + }else if (!pfn_is_ram (__pa (start) >>PAGE_SHIFT )) { +if (clear_user (buffer, tsz)) { + ret = -EFAULT ; + goto out; + } }else if (m->type ==KCORE_VMALLOC ) {vread (buf, (char *)start, tsz);/* we have to zero-fill user buffer even if no read */ include/linux/kcore.h +2
-1@@ -44,6 +44,8 @@ void kclist_add_remap(struct kcore_list *m, void *addr, void *vaddr, size_t sz) m->vaddr = (unsigned long )vaddr; kclist_add(m, addr, sz, KCORE_REMAP); } + +extern int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn));#else static inline void kclist_add (struct kcore_list *new,void *addr,size_t size,int type) --
Quoted 2 lines
2.20.1
Ping? Can any one help to take this patch?
--
Best Regards,
Kairui Song
tip-bot for Kairui Song
merge bot[tip:x86/urgent] x86/gart: Exclude GART aperture from kcore
In reply to Kairui Songx86/gart: Exclude GART aperture from kcore
Commit-ID: ffc8599aa9763f39f6736a79da4d1575e7006f9a Gitweb: https://git.kernel.org/tip/ffc8599aa9763f39f6736a79da4d1575e7006f9a Author: Kairui Song <[email protected]> AuthorDate: Fri, 8 Mar 2019 11:05:08 +0800 Committer: Thomas Gleixner <[email protected]> CommitDate: Sat, 23 Mar 2019 12:11:49 +0100
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.
--- arch/x86/kernel/aperture_64.c | 20 +++++++++++++------- fs/proc/kcore.c | 27 +++++++++++++++++++++++++++ include/linux/kcore.h | 2 ++ 3 files changed, 42 insertions(+), 7 deletions(-)
arch/x86/kernel/aperture_64.c +13 -7
@@ -14,6 +14,7 @@#define pr_fmt (fmt) "AGP: " fmt#include <linux/kernel.h> +#include <linux/kcore.h> #include <linux/types.h> #include <linux/init.h> #include <linux/memblock.h>
@@ -57,7 +58,7 @@ int fallback_aper_force __initdata;int fix_aperture__initdata =1 ; -#ifdef CONFIG_PROC_VMCORE +#if defined(CONFIG_PROC_VMCORE ) || defined(CONFIG_PROC_KCORE )/* * If the first kernel maps the aperture over e820 RAM, the kdump kernel will * use the same range because it will remain configured in the northbridge.
@@ -66,20 +67,25 @@ int fix_aperture __initdata = 1;*/ static unsigned long aperture_pfn_start, aperture_page_count; -static int gart_oldmem_pfn_is_ram (unsigned long pfn) +static int gart_mem_pfn_is_ram (unsigned long pfn) {return likely ((pfn < aperture_pfn_start) || (pfn >= aperture_pfn_start + aperture_page_count)); } -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void __init exclude_from_core (u64 aper_base,u32 aper_order) { aperture_pfn_start = aper_base >>PAGE_SHIFT ; aperture_page_count = (32 *1024 *1024 ) << aper_order >>PAGE_SHIFT ; -WARN_ON (register_oldmem_pfn_is_ram (&gart_oldmem_pfn_is_ram)); +#ifdef CONFIG_PROC_VMCORE +WARN_ON (register_oldmem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif +#ifdef CONFIG_PROC_KCORE +WARN_ON (register_mem_pfn_is_ram (&gart_mem_pfn_is_ram)); +#endif }#else -static void exclude_from_vmcore (u64 aper_base,u32 aper_order) +static void exclude_from_core (u64 aper_base,u32 aper_order) { }#endif
@@ -474,7 +480,7 @@ out:* may have allocated the range over its e820 RAM * and fixed up the northbridge */ -exclude_from_vmcore (last_aper_base, last_aper_order); +exclude_from_core (last_aper_base, last_aper_order);return 1 ; }
@@ -520,7 +526,7 @@ out:* overlap with the first kernel's memory. We can't access the * range through vmcore even though it should be part of the dump. */ -exclude_from_vmcore (aper_alloc, aper_order); +exclude_from_core (aper_alloc, aper_order);/* Fix up the north bridges */ for (i =0 ; i < amd_nb_bus_dev_ranges[i].dev_limit; i++) {
fs/proc/kcore.c +27 -0
@@ -54,6 +54,28 @@ static LIST_HEAD(kclist_head);static DECLARE_RWSEM (kclist_lock);static int kcore_need_update =1 ; +/* +* Returns > 0 for RAM pages, 0 for non-RAM pages, < 0 on error +* Same as oldmem_pfn_is_ram in vmcore +*/ +static int (*mem_pfn_is_ram)(unsigned long pfn); + +int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn)) +{ +if (mem_pfn_is_ram) +return -EBUSY ; + mem_pfn_is_ram = fn; +return 0 ; +} + +static int pfn_is_ram (unsigned long pfn) +{ +if (mem_pfn_is_ram) +return mem_pfn_is_ram (pfn); +else +return 1 ; +} +/* This doesn't grab kclist_lock, so it should only be used at init time. */ void __init kclist_add (struct kcore_list *new,void *addr,size_t size,int type)
@@ -465,6 +487,11 @@ read_kcore(struct file *file, char __user *buffer, size_t buflen, loff_t *fpos) goto out; } m =NULL ;/* skip the list anchor */ + }else if (!pfn_is_ram (__pa (start) >>PAGE_SHIFT )) { +if (clear_user (buffer, tsz)) { + ret = -EFAULT ; + goto out; + } }else if (m->type ==KCORE_VMALLOC ) {vread (buf, (char *)start, tsz);/* we have to zero-fill user buffer even if no read */
include/linux/kcore.h +2 -0
@@ -44,6 +44,8 @@ void kclist_add_remap(struct kcore_list *m, void *addr, void *vaddr, size_t sz) m->vaddr = (unsigned long )vaddr; kclist_add(m, addr, sz, KCORE_REMAP); } + +extern int __init register_mem_pfn_is_ram (int (*fn)(unsigned long pfn));#else static inline void kclist_add (struct kcore_list *new,void *addr,size_t size,int type)