From: Peter Zijlstra <peterz@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [rcu:rcu/next 4/4] frv-linux-ld: Warning: size of symbol `sys_membarrier' changed from 8 in kernel/sys_ni.o to 44 in kernel/sched/membarrier.o
Date: Fri, 28 Jul 2017 11:19:33 +0200 [thread overview]
Message-ID: <20170728091933.3ptftxlynlinkw56@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1263288023.29217.1501202800701.JavaMail.zimbra@efficios.com>
On Fri, Jul 28, 2017 at 12:46:40AM +0000, Mathieu Desnoyers wrote:
> > This is a new one on me. What do we do to fix it?
Apparently (see below) the answer is, we ignore this.
> I would suspect this might be caused by moving membarrier.c from kernel/
> to kernel/sched/. Perhaps Peter knows ?
<peterz> dhowells: hey, I know you don't care about FRV anymore, but suppose the 0-day thing says things like:
<peterz> >> frv-linux-ld: Warning: size of symbol `sys_setuid' changed from 272 in
<peterz> >> kernel/sys.o to 8 in kernel/sys_ni.o
<peterz> dhowells: do you have any clue wth went wrong?
<dhowells> peterz: it's been saying that for a long time, but I've no idea why
<dhowells> didn't seem to stop it working
<dhowells> I suspect it might not be handing weak symbol elimination correctly or something
<peterz> fair enough, I'll ignore it then
next prev parent reply other threads:[~2017-07-28 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 0:16 kbuild test robot
2017-07-28 0:38 ` Paul E. McKenney
2017-07-28 0:46 ` Mathieu Desnoyers
2017-07-28 0:50 ` Mathieu Desnoyers
2017-07-28 9:19 ` Peter Zijlstra [this message]
2017-07-28 9:42 ` [kbuild-all] " Fengguang Wu
2017-07-28 12:43 ` Paul E. McKenney
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=20170728091933.3ptftxlynlinkw56@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.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
all inboxes | Powered by JetHome®