All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: vgoyal@redhat.com, ebiederm@xmission.com,
	akpm@linux-foundation.org, cpw@sgi.com,
	kumagai-atsushi@mxc.nes.nec.co.jp, lisa.mitchell@hp.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	zhangyanfei@cn.fujitsu.com, jingbai.ma@hp.com,
	linux-mm@kvack.org, riel@redhat.com, walken@google.com,
	hughd@google.com, kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore
Date: Fri, 7 Jun 2013 20:34:58 +0200	[thread overview]
Message-ID: <201306072034.58817.arnd@arndb.de> (raw)
In-Reply-To: <51B130F9.8070408@jp.fujitsu.com>

On Friday 07 June 2013, HATAYAMA Daisuke wrote:
> Thanks for trying the build and your report!
> 
> OTOH, I don't have no-MMU architectures; x86 box only. I cannot reproduce this build error. 
> Could you give me your build log? I want to use it to detect what part depends on CONFIG_MMU.

What I get is a link-time error:

fs/built-in.o: In function `mmap_vmcore':
:(.text+0x4bc18): undefined reference to `remap_vmalloc_range_partial'
fs/built-in.o: In function `merge_note_headers_elf32.constprop.4':
:(.init.text+0x142c): undefined reference to `find_vm_area'

and I used this patch to temporarily work around the problem, effectively disabling all
of /proc/vmcore on non-MMU kernels.

diff --git a/include/linux/crash_dump.h b/include/linux/crash_dump.h
index 37e4f8d..9a078ef 100644
--- a/include/linux/crash_dump.h
+++ b/include/linux/crash_dump.h
@@ -55,7 +55,7 @@ static inline int is_kdump_kernel(void)
 
 static inline int is_vmcore_usable(void)
 {
-	return is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
+	return IS_ENABLED(CONFIG_MMU) && is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
 }
 
 /* vmcore_unusable() marks the vmcore as unusable,


For testing, I used ARM at91x40_defconfig and manually turned on VMCORE support in
menuconfig, but it happened before using "randconfig". On most distros you can
these days install an arm cross compiler using yum or apt-get and build
the kernel yourself with 'make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-'

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: vgoyal@redhat.com, ebiederm@xmission.com,
	akpm@linux-foundation.org, cpw@sgi.com,
	kumagai-atsushi@mxc.nes.nec.co.jp, lisa.mitchell@hp.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	zhangyanfei@cn.fujitsu.com, jingbai.ma@hp.com,
	linux-mm@kvack.org, riel@redhat.com, walken@google.com,
	hughd@google.com, kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore
Date: Fri, 7 Jun 2013 20:34:58 +0200	[thread overview]
Message-ID: <201306072034.58817.arnd@arndb.de> (raw)
In-Reply-To: <51B130F9.8070408@jp.fujitsu.com>

On Friday 07 June 2013, HATAYAMA Daisuke wrote:
> Thanks for trying the build and your report!
> 
> OTOH, I don't have no-MMU architectures; x86 box only. I cannot reproduce this build error. 
> Could you give me your build log? I want to use it to detect what part depends on CONFIG_MMU.

What I get is a link-time error:

fs/built-in.o: In function `mmap_vmcore':
:(.text+0x4bc18): undefined reference to `remap_vmalloc_range_partial'
fs/built-in.o: In function `merge_note_headers_elf32.constprop.4':
:(.init.text+0x142c): undefined reference to `find_vm_area'

and I used this patch to temporarily work around the problem, effectively disabling all
of /proc/vmcore on non-MMU kernels.

diff --git a/include/linux/crash_dump.h b/include/linux/crash_dump.h
index 37e4f8d..9a078ef 100644
--- a/include/linux/crash_dump.h
+++ b/include/linux/crash_dump.h
@@ -55,7 +55,7 @@ static inline int is_kdump_kernel(void)
 
 static inline int is_vmcore_usable(void)
 {
-	return is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
+	return IS_ENABLED(CONFIG_MMU) && is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
 }
 
 /* vmcore_unusable() marks the vmcore as unusable,


For testing, I used ARM at91x40_defconfig and manually turned on VMCORE support in
menuconfig, but it happened before using "randconfig". On most distros you can
these days install an arm cross compiler using yum or apt-get and build
the kernel yourself with 'make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-'

	Arnd

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: riel@redhat.com, hughd@google.com, jingbai.ma@hp.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	lisa.mitchell@hp.com, linux-mm@kvack.org,
	kumagai-atsushi@mxc.nes.nec.co.jp, ebiederm@xmission.com,
	kosaki.motohiro@jp.fujitsu.com, zhangyanfei@cn.fujitsu.com,
	akpm@linux-foundation.org, walken@google.com, cpw@sgi.com,
	vgoyal@redhat.com
Subject: Re: [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore
Date: Fri, 7 Jun 2013 20:34:58 +0200	[thread overview]
Message-ID: <201306072034.58817.arnd@arndb.de> (raw)
In-Reply-To: <51B130F9.8070408@jp.fujitsu.com>

On Friday 07 June 2013, HATAYAMA Daisuke wrote:
> Thanks for trying the build and your report!
> 
> OTOH, I don't have no-MMU architectures; x86 box only. I cannot reproduce this build error. 
> Could you give me your build log? I want to use it to detect what part depends on CONFIG_MMU.

What I get is a link-time error:

fs/built-in.o: In function `mmap_vmcore':
:(.text+0x4bc18): undefined reference to `remap_vmalloc_range_partial'
fs/built-in.o: In function `merge_note_headers_elf32.constprop.4':
:(.init.text+0x142c): undefined reference to `find_vm_area'

and I used this patch to temporarily work around the problem, effectively disabling all
of /proc/vmcore on non-MMU kernels.

diff --git a/include/linux/crash_dump.h b/include/linux/crash_dump.h
index 37e4f8d..9a078ef 100644
--- a/include/linux/crash_dump.h
+++ b/include/linux/crash_dump.h
@@ -55,7 +55,7 @@ static inline int is_kdump_kernel(void)
 
 static inline int is_vmcore_usable(void)
 {
-	return is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
+	return IS_ENABLED(CONFIG_MMU) && is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
 }
 
 /* vmcore_unusable() marks the vmcore as unusable,


For testing, I used ARM at91x40_defconfig and manually turned on VMCORE support in
menuconfig, but it happened before using "randconfig". On most distros you can
these days install an arm cross compiler using yum or apt-get and build
the kernel yourself with 'make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-'

	Arnd

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2013-06-07 18:35 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  5:24 [PATCH v8 0/9] kdump, vmcore: support mmap() on /proc/vmcore HATAYAMA Daisuke
2013-05-23  5:24 ` HATAYAMA Daisuke
2013-05-23  5:24 ` HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 1/9] vmcore: clean up read_vmcore() HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 2/9] vmcore: allocate buffer for ELF headers on page-size alignment HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 14:22   ` Vivek Goyal
2013-05-23 14:22     ` Vivek Goyal
2013-05-23 14:22     ` Vivek Goyal
2013-05-23 21:46   ` Andrew Morton
2013-05-23 21:46     ` Andrew Morton
2013-05-23 21:46     ` Andrew Morton
2013-05-23  5:25 ` [PATCH v8 3/9] vmcore: treat memory chunks referenced by PT_LOAD program header entries in page-size boundary in vmcore_list HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 21:49   ` Andrew Morton
2013-05-23 21:49     ` Andrew Morton
2013-05-23 21:49     ` Andrew Morton
2013-05-24 13:12     ` Vivek Goyal
2013-05-24 13:12       ` Vivek Goyal
2013-05-24 13:12       ` Vivek Goyal
2013-05-27  0:13       ` HATAYAMA Daisuke
2013-05-27  0:13         ` HATAYAMA Daisuke
2013-05-27  0:13         ` HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 4/9] vmalloc: make find_vm_area check in range HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25 ` [PATCH v8 5/9] vmalloc: introduce remap_vmalloc_range_partial HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 22:00   ` Andrew Morton
2013-05-23 22:00     ` Andrew Morton
2013-05-23 22:00     ` Andrew Morton
2013-05-23  5:25 ` [PATCH v8 6/9] vmcore: allocate ELF note segment in the 2nd kernel vmalloc memory HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 14:28   ` Vivek Goyal
2013-05-23 14:28     ` Vivek Goyal
2013-05-23 14:28     ` Vivek Goyal
2013-05-23 22:17   ` Andrew Morton
2013-05-23 22:17     ` Andrew Morton
2013-05-23 22:17     ` Andrew Morton
2013-05-23  5:25 ` [PATCH v8 7/9] vmcore: Allow user process to remap ELF note segment buffer HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 14:32   ` Vivek Goyal
2013-05-23 14:32     ` Vivek Goyal
2013-05-23 14:32     ` Vivek Goyal
2013-05-23  5:25 ` [PATCH v8 8/9] vmcore: calculate vmcore file size from buffer size and total size of vmcore objects HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 14:34   ` Vivek Goyal
2013-05-23 14:34     ` Vivek Goyal
2013-05-23 14:34     ` Vivek Goyal
2013-05-23  5:25 ` [PATCH v8 9/9] vmcore: support mmap() on /proc/vmcore HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23  5:25   ` HATAYAMA Daisuke
2013-05-23 22:24   ` Andrew Morton
2013-05-23 22:24     ` Andrew Morton
2013-05-23 22:24     ` Andrew Morton
2013-05-24  9:02     ` Maxim Uvarov
2013-05-27  1:49       ` HATAYAMA Daisuke
2013-05-27  1:49         ` HATAYAMA Daisuke
2013-05-27  1:49         ` HATAYAMA Daisuke
2013-05-30  9:14         ` Maxim Uvarov
2013-05-30  9:26           ` Zhang Yanfei
2013-05-30  9:26             ` Zhang Yanfei
2013-05-30  9:26             ` Zhang Yanfei
2013-05-30 10:30             ` Maxim Uvarov
2013-06-03  8:43               ` Atsushi Kumagai
2013-06-03  8:43                 ` Atsushi Kumagai
2013-06-03  8:43                 ` Atsushi Kumagai
2013-06-04 15:34                 ` Maxim Uvarov
2013-06-07  1:11                   ` Zhang Yanfei
2013-06-07  1:11                     ` Zhang Yanfei
2013-06-07  1:11                     ` Zhang Yanfei
2013-06-28 16:40                 ` Maxim Uvarov
2013-06-30 23:53                   ` HATAYAMA Daisuke
2013-06-30 23:53                     ` HATAYAMA Daisuke
2013-06-30 23:53                     ` HATAYAMA Daisuke
2013-07-01 14:34                     ` Maxim Uvarov
2013-07-01 19:53                       ` Andrew Morton
2013-07-01 19:53                         ` Andrew Morton
2013-07-01 19:53                         ` Andrew Morton
2013-07-02  7:00                         ` Maxim Uvarov
2013-06-06 21:31   ` Arnd Bergmann
2013-06-06 21:31     ` Arnd Bergmann
2013-06-06 21:31     ` Arnd Bergmann
2013-06-07  1:01     ` HATAYAMA Daisuke
2013-06-07  1:01       ` HATAYAMA Daisuke
2013-06-07  1:01       ` HATAYAMA Daisuke
2013-06-07 18:34       ` Arnd Bergmann [this message]
2013-06-07 18:34         ` Arnd Bergmann
2013-06-07 18:34         ` Arnd Bergmann
2013-06-08 10:42         ` HATAYAMA Daisuke
2013-06-08 10:42           ` HATAYAMA Daisuke
2013-06-08 10:42           ` HATAYAMA Daisuke
2013-05-23 14:35 ` [PATCH v8 0/9] kdump, " Vivek Goyal
2013-05-23 14:35   ` Vivek Goyal
2013-05-23 14:35   ` Vivek Goyal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201306072034.58817.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=hughd@google.com \
    --cc=jingbai.ma@hp.com \
    --cc=kexec@lists.infradead.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lisa.mitchell@hp.com \
    --cc=riel@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=walken@google.com \
    --cc=zhangyanfei@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.