From: Miroslav Benes <mbenes@suse.cz>
To: Petr Mladek <pmladek@suse.com>
Cc: Song Liu <song@kernel.org>, X86 ML <x86@kernel.org>,
live-patching@vger.kernel.org, jpoimboe@kernel.org,
jikos@kernel.org, joe.lawrence@redhat.com,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH v8] livepatch: Clear relocation targets on a module removal
Date: Wed, 18 Jan 2023 14:37:57 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2301181437110.13709@pobox.suse.cz> (raw)
In-Reply-To: <Y8f1g62ouKsmjwpL@alley>
> > >
> > > > +int klp_apply_section_relocs(struct module *pmod, Elf_Shdr *sechdrs,
> > > > + const char *shstrtab, const char *strtab,
> > > > + unsigned int symndx, unsigned int secndx,
> > > > + const char *objname)
> > > > +{
> > > > + return klp_write_section_relocs(pmod, sechdrs, shstrtab, strtab, symndx,
> > > > + secndx, objname, true);
> > > > }
>
> I think that I proposed this wrapper :-)
>
> > > Is this redirection needed somewhere? You could just replace
> > > klp_apply_section_relocs() with klp_write_section_relocs() in
> > > include/linux/livepatch.h and kernel/module/main.c.
> > >
> > > It may be cleaned up later.
> >
> > It might be a good practice to keep _write_ static in this file, and
> > only expose _apply_ (maybe also _clear_ in the future)?
>
> And I think that this was the reason. Also it looks better in
> kernel/module/main.c in apply_relocations() that calls few more
> *_apply_*reloc*() functions.
>
> The idea is that functions with the same naming pattern do
> the same operation. Also it is supposed to hide the true/false
> parameter and self-explain the meaning by the function name.
>
>
> > I don't have a strong preference either way.
>
> I would prefer to keep the wrapper. But I do not resist on it :-)
Ok, fair enough. Let's keep it then.
Miroslav
next prev parent reply other threads:[~2023-01-18 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 20:01 [PATCH v8] livepatch: Clear relocation targets on a module removal Song Liu
2023-01-10 17:51 ` Song Liu
2023-01-10 20:44 ` Joe Lawrence
2023-01-13 9:18 ` Miroslav Benes
2023-01-13 19:55 ` Song Liu
2023-01-18 13:34 ` Petr Mladek
2023-01-18 13:37 ` Miroslav Benes [this message]
2023-01-18 13:02 ` Petr Mladek
2023-01-18 19:23 ` Song Liu
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=alpine.LSU.2.21.2301181437110.13709@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=live-patching@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=song@kernel.org \
--cc=x86@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