From: Luis Chamberlain <mcgrof@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Arnd Bergmann <arnd@kernel.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
linux-modules@vger.kernel.org,
Zhen Lei <thunder.leizhen@huawei.com>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kallsyms: remove unused arch_get_kallsym() helper
Date: Wed, 24 May 2023 00:24:20 -0700 [thread overview]
Message-ID: <ZG27pExhUqFpGexM@bombadil.infradead.org> (raw)
In-Reply-To: <a3d01d39-3d45-4fdc-8f73-b6c33bcae24b@app.fastmail.com>
On Wed, May 24, 2023 at 08:25:13AM +0200, Arnd Bergmann wrote:
> On Wed, May 24, 2023, at 07:07, Luis Chamberlain wrote:
> > On Wed, May 17, 2023 at 03:18:07PM +0200, Arnd Bergmann wrote:
> >> From: Arnd Bergmann <arnd@arndb.de>
> >>
> >> The arch_get_kallsym() function was introduced so that x86 could override
> >> it, but that override was removed in bf904d2762ee ("x86/pti/64: Remove
> >> the SYSCALL64 entry trampoline"), so now this does nothing except causing
> >> a warning about a missing prototype:
> >>
> >> kernel/kallsyms.c:662:12: error: no previous prototype for 'arch_get_kallsym' [-Werror=missing-prototypes]
> >> 662 | int __weak arch_get_kallsym(unsigned int symnum, unsigned long *value,
> >>
> >> Restore the old behavior before d83212d5dd67 ("kallsyms, x86: Export
> >> addresses of PTI entry trampolines") to simplify the code and avoid
> >> the warning.
> >>
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >
> > Shouldn't this go through x86 as this sort of fixesss commit
> > bf904d2762ee ("x86/pti/64: Remove the SYSCALL64 entry trampoline")?
>
> That works for me as well, as long as someone picks it up. It's
> not really x86 any more though since that commit is five years
> old and removed the last reference from the x86 code.
Fair enough.
> I sent it to you since you are the one that merged most of
> the kallsyms patches through the module tree, but I guess
> you are not actually maintaining that file (not blaming you,
> I'd also try to stay away from kallsyms).
>
> I can resend it to Andrew for the -mm tree.
OK, I just took the patch in, it's on the train, better get on before
it gets lost.
Luis
next prev parent reply other threads:[~2023-05-24 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:18 [PATCH] kallsyms: remove unused arch_get_kallsym() helper Arnd Bergmann
2023-05-24 5:07 ` Luis Chamberlain
2023-05-24 6:25 ` Arnd Bergmann
2023-05-24 7:24 ` Luis Chamberlain [this message]
2023-05-26 1:45 ` Song Liu
2023-05-26 3:24 ` Luis Chamberlain
2023-05-26 6:41 ` Arnd Bergmann
2023-05-26 14:39 ` Alan Maguire
2023-05-26 17:39 ` Luis Chamberlain
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=ZG27pExhUqFpGexM@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=thunder.leizhen@huawei.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;
as well as URLs for NNTP newsgroup(s).