From: Peter Zijlstra <peterz@infradead.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Wander Lairson Costa <wander@redhat.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-riscv@lists.infradead.org
Subject: Re: [peterz-queue:sched/maybe 1/14] ERROR: modpost: vmlinux: local symbol '__put_task_struct_rcu_cb' was exported
Date: Tue, 11 Jul 2023 08:50:40 +0200 [thread overview]
Message-ID: <20230711065040.GA3062772@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230710185657.GA1505918@dev-arch.thelio-3990X>
On Mon, Jul 10, 2023 at 11:56:57AM -0700, Nathan Chancellor wrote:
> On Mon, Jul 10, 2023 at 08:26:05PM +0200, Peter Zijlstra wrote:
> > On Tue, Jul 11, 2023 at 01:48:23AM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/maybe
> > > head: 69ff1e365682e2d516364c010b51f8a95140cd94
> > > commit: eb15cb094ddb0227c9dfe5eb836d1a4357f070fd [1/14] kernel/fork: beware of __put_task_struct calling context
> > > config: riscv-randconfig-r042-20230710 (https://download.01.org/0day-ci/archive/20230711/202307110147.tDoRemZ7-lkp@intel.com/config)
> > > compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
> > > reproduce: (https://download.01.org/0day-ci/archive/20230711/202307110147.tDoRemZ7-lkp@intel.com/reproduce)
> > >
> >
> > > >> ERROR: modpost: vmlinux: local symbol '__put_task_struct_rcu_cb' was exported
> >
> > The commit above introduces this function:
> >
> > +void __put_task_struct_rcu_cb(struct rcu_head *rhp)
> > +{
> > + struct task_struct *task = container_of(rhp, struct task_struct, rcu);
> > +
> > + __put_task_struct(task);
> > +}
> > +EXPORT_SYMBOL_GPL(__put_task_struct_rcu_cb);
> >
> > How the heck does that become a local symbol?
> >
>
> Looking at the configuration:
>
> CONFIG_32BIT=y
> CONFIG_ARCH_RV32I=y
>
> It is highly likely that something is broken with 32-bit RISC-V and
> clang, as that is not something we have ever tested. I don't even think
> 32-bit RISC-V is tested that much even with GCC, so I'm not sure if this
> is even worth looking into.
Fair enough; I'll put it on the ignore list. Thanks!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-07-11 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202307110147.tDoRemZ7-lkp@intel.com>
[not found] ` <20230710182605.GA3044890@hirez.programming.kicks-ass.net>
2023-07-10 18:56 ` [peterz-queue:sched/maybe 1/14] ERROR: modpost: vmlinux: local symbol '__put_task_struct_rcu_cb' was exported Nathan Chancellor
2023-07-11 6:50 ` Peter Zijlstra [this message]
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=20230711065040.GA3062772@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wander@redhat.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