[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250605143900.GV39944@noisy.programming.kicks-ass.net>
Date: Thu, 5 Jun 2025 16:39:00 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Petr Pavlu <petr.pavlu@...e.com>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
linux-modules@...r.kernel.org, oe-lkp@...ts.linux.dev,
lkp@...el.com, linux-kernel@...r.kernel.org,
kernel test robot <oliver.sang@...el.com>,
Paolo Abeni <pabeni@...hat.com>,
Allison Henderson <allison.henderson@...cle.com>,
netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
rds-devel@....oracle.com, Luis Chamberlain <mcgrof@...nel.org>,
Sami Tolvanen <samitolvanen@...gle.com>,
Daniel Gomez <da.gomez@...sung.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2] module: Make sure relocations are applied to the
per-CPU section
On Thu, Jun 05, 2025 at 03:44:23PM +0200, Petr Pavlu wrote:
> For instance:
>
> /*
> * Don't bother with non-allocated sections.
> *
> * An exception is the percpu section, which has separate allocations
> * for individual CPUs. We relocate the percpu section in the initial
> * ELF template and subsequently copy it to the per-CPU destinations.
> */
> if (!(info->sechdrs[infosec].sh_flags & SHF_ALLOC) &&
> infosec != info->index.pcpu)
> continue;
Right, and pcpu is a data section and should not have relative
relocations, only absolute.
So copying things should not be a problem.
Powered by blists - more mailing lists