From: Mel Gorman <mgorman@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kbuild-all@lists.01.org, kbuild test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-stable-rc:linux-4.14.y 9946/9999] WARNING: vmlinux.o(.text+0x213438): Section mismatch in reference from the function __rmqueue() to the function .meminit.text:zone_pcp_update()
Date: Tue, 12 Nov 2019 08:58:14 +0000 [thread overview]
Message-ID: <20191112085814.GC28938@suse.de> (raw)
In-Reply-To: <201911120222.zJAaxNTt%lkp@intel.com>
On Tue, Nov 12, 2019 at 02:57:23AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y
> head: 0d12dcf336c606a37cf2ad4319bc59f69eb6c255
> commit: 88284ade98e99e3e391c90b51b8b7420953071d4 [9946/9999] mm, meminit: recalculate pcpu batch and high limits after init completes
> config: sparc64-allmodconfig (attached as .config)
> compiler: sparc64-linux-gcc (GCC) 7.4.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 88284ade98e99e3e391c90b51b8b7420953071d4
> # save the attached .config to linux build tree
> GCC_VERSION=7.4.0 make.cross ARCH=sparc64
>
> 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+0x213438): Section mismatch in reference from the function __rmqueue() to the function .meminit.text:zone_pcp_update()
> The function __rmqueue() references
> the function __meminit zone_pcp_update().
> This is often because __rmqueue lacks a __meminit
> annotation or the annotation of zone_pcp_update is wrong.
>
Greg,
It's probably best to drop this patch from 4.14-stable for now. In theory,
4.14-stable is affected but deferred meminit went through a lot of changes
and it hasn't been proven it is definitely necessary. I know at least
that a 4.12-based distribution kernel is not affected by the bug but
didn't isolate why given that 4.12-vanilla failed to boot on the test
machines I had access to.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-11-12 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 18:57 kbuild test robot
2019-11-12 8:58 ` Mel Gorman [this message]
2019-11-12 10:21 ` Greg Kroah-Hartman
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=20191112085814.GC28938@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox