From: Luis Chamberlain <mcgrof@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: James Morse <james.morse@arm.com>,
linux-modules@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jessica Yu <jeyu@kernel.org>,
Adam Johnston <adam.johnston@arm.com>
Subject: Re: [PATCH 0/3] ARM/arm64: Fix loading of modules with an exit section
Date: Thu, 3 Aug 2023 13:43:39 -0700 [thread overview]
Message-ID: <ZMwRezKXKye1bsSN@bombadil.infradead.org> (raw)
In-Reply-To: <ZMt/VgQoovUDi4g7@shell.armlinux.org.uk>
On Thu, Aug 03, 2023 at 11:20:06AM +0100, Russell King (Oracle) wrote:
> On Wed, Aug 02, 2023 at 05:28:10PM +0100, James Morse wrote:
> > If Russell agrees the problem exists on 32bit arm, then I think it
> > would be best to keep these three together - going via the modules
> > tree would make the most sense.
>
> The thing about PLTs is that it's something I've never had the need to
> make use of - because I've never been in the situation where the
> arm32 module space has been close to overflowing. The addition of PLT
> support for 32-bit arm did make my eyebrows raise for this very reason,
> but I guess there are a small number of people who want to use really
> large modules.
>
> As such, I couldn't say whether it's broken or not - but it seems
> sensible to keep both the 64-bit and 32-bit code tracking each other.
Alrighty, merged and pushed onto modules-next.
Luis
prev parent reply other threads:[~2023-08-03 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 14:54 [PATCH 0/3] ARM/arm64: Fix loading of modules with an exit section James Morse
2023-08-01 14:54 ` [PATCH 1/3] module: Expose module_init_layout_section() James Morse
2023-08-01 14:54 ` [PATCH 2/3] arm64: module: Use module_init_layout_section() to spot init sections James Morse
2023-08-02 17:00 ` Catalin Marinas
2023-08-01 14:54 ` [PATCH 3/3] ARM: " James Morse
2023-08-01 17:14 ` [PATCH 0/3] ARM/arm64: Fix loading of modules with an exit section Luis Chamberlain
2023-08-02 16:28 ` James Morse
2023-08-03 10:20 ` Russell King (Oracle)
2023-08-03 20:43 ` Luis Chamberlain [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=ZMwRezKXKye1bsSN@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=adam.johnston@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jeyu@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=will@kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).