From: Peter Zijlstra <peterz@infradead.org>
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-modules@vger.kernel.org, oe-lkp@lists.linux.dev,
lkp@intel.com, linux-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
Allison Henderson <allison.henderson@oracle.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] module: Make sure relocations are applied to the per-CPU section
Date: Thu, 5 Jun 2025 16:39:00 +0200 [thread overview]
Message-ID: <20250605143900.GV39944@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <beb343ec-6349-4f9c-9fea-588b04eb49ee@suse.com>
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.
next prev parent reply other threads:[~2025-06-05 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:42 [linus:master] [rds] c50d295c37: BUG:unable_to_handle_page_fault_for_address kernel test robot
2025-06-04 11:04 ` Sebastian Andrzej Siewior
2025-06-04 15:27 ` [PATCH] module: Make sure relocations are applied to the per-CPU section Sebastian Andrzej Siewior
2025-06-05 6:07 ` [PATCH v2] " Sebastian Andrzej Siewior
2025-06-05 13:44 ` Petr Pavlu
2025-06-05 14:39 ` Peter Zijlstra [this message]
2025-06-05 15:54 ` Sebastian Andrzej Siewior
2025-06-05 16:50 ` Petr Pavlu
2025-06-10 14:55 ` Sebastian Andrzej Siewior
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=20250605143900.GV39944@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=allison.henderson@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=pabeni@redhat.com \
--cc=petr.pavlu@suse.com \
--cc=rds-devel@oss.oracle.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
/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