From: lijiang <lijiang@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: jgross@suse.com, Thomas.Lendacky@amd.com,
kbuild-all@lists.01.org, bhe@redhat.com, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
dhowells@redhat.com, mingo@redhat.com,
Borislav Petkov <bp@alien8.de>,
ebiederm@xmission.com, hpa@zytor.com, tglx@linutronix.de,
dyoung@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH] x86/kdump: always reserve the low 1MiB when the crashkernel
Date: Fri, 25 Oct 2019 07:55:42 +0800 [thread overview]
Message-ID: <3fce1517-2a76-53da-1538-aa75f3427d5b@redhat.com> (raw)
In-Reply-To: <201910250603.En7IO6Xd%lkp@intel.com>
在 2019年10月25日 06:12, kbuild test robot 写道:
> Hi lijiang,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on linus/master]
> [cannot apply to v5.4-rc4 next-20191024]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/lijiang/x86-kdump-always-reserve-the-low-1MiB-when-the-crashkernel/20191025-030439
> base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git f116b96685a046a89c25d4a6ba2da489145c8888
> config: i386-defconfig (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> WARNING: vmlinux.o(.text+0xe39b7): Section mismatch in reference from the function kexec_reserve_low_1MiB() to the variable .init.data:boot_command_line
> The function kexec_reserve_low_1MiB() references
> the variable __initdata boot_command_line.
> This is often because kexec_reserve_low_1MiB lacks a __initdata
> annotation or the annotation of boot_command_line is wrong.
> --
>>> WARNING: vmlinux.o(.text+0xe39d0): Section mismatch in reference from the function kexec_reserve_low_1MiB() to the function .meminit.text:memblock_reserve()
> The function kexec_reserve_low_1MiB() references
> the function __meminit memblock_reserve().
> This is often because kexec_reserve_low_1MiB lacks a __meminit
> annotation or the annotation of memblock_reserve is wrong.
>
These warnings have been fixed in patch v5. Please refer to the latest patch v5.
Thanks.
Lianbo
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-10-24 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:43 [PATCH 0/3 v4] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active Lianbo Jiang
2019-10-17 9:43 ` [PATCH 1/3 v4] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified Lianbo Jiang
2019-10-22 8:30 ` Borislav Petkov
2019-10-23 5:23 ` lijiang
2019-10-23 7:43 ` Borislav Petkov
2019-10-23 5:35 ` lijiang
2019-10-23 7:46 ` Borislav Petkov
2019-10-23 9:20 ` lijiang
2019-10-24 8:13 ` d.hatayama
2019-10-24 9:10 ` Borislav Petkov
2019-10-24 11:24 ` lijiang
2019-10-24 22:12 ` [PATCH] x86/kdump: always reserve the low 1MiB when the crashkernel kbuild test robot
2019-10-24 23:55 ` lijiang [this message]
2019-10-17 9:43 ` [PATCH 2/3 v4] x86/kdump: remove the unused crash_copy_backup_region() Lianbo Jiang
2019-10-17 9:43 ` [PATCH 3/3 v4] x86/kdump: clean up all the code related to the backup region Lianbo Jiang
2019-10-22 12:15 ` Borislav Petkov
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=3fce1517-2a76-53da-1538-aa75f3427d5b@redhat.com \
--to=lijiang@redhat.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dhowells@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox