From: Miroslav Benes <mbenes@suse.cz>
To: Song Liu <song@kernel.org>
Cc: Petr Mladek <pmladek@suse.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
jpoimboe@kernel.org, jikos@kernel.org, x86@kernel.org,
joe.lawrence@redhat.com, linuxppc-dev@lists.ozlabs.org,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH v6] livepatch: Clear relocation targets on a module removal
Date: Fri, 9 Dec 2022 13:49:32 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2212091348090.18933@pobox.suse.cz> (raw)
In-Reply-To: <CAPhsuW4qYpX7wzHn5J5Hn9cnOFSZwwQPCjTM_HPTt_zbBS03ww@mail.gmail.com>
> > > --- a/kernel/livepatch/core.c
> > > +++ b/kernel/livepatch/core.c
> > > @@ -316,6 +316,45 @@ int klp_apply_section_relocs(struct module *pmod, Elf_Shdr *sechdrs,
> > > return apply_relocate_add(sechdrs, strtab, symndx, secndx, pmod);
> > > }
> > >
> > > +static void klp_clear_object_relocations(struct module *pmod,
> > > + struct klp_object *obj)
> > > +{
> > > + int i, cnt;
> > > + const char *objname, *secname;
> > > + char sec_objname[MODULE_NAME_LEN];
> > > + Elf_Shdr *sec;
> > > +
> > > + objname = klp_is_module(obj) ? obj->name : "vmlinux";
> > > +
> > > + /* For each klp relocation section */
> > > + for (i = 1; i < pmod->klp_info->hdr.e_shnum; i++) {
> > > + sec = pmod->klp_info->sechdrs + i;
> > > + secname = pmod->klp_info->secstrings + sec->sh_name;
> > > + if (!(sec->sh_flags & SHF_RELA_LIVEPATCH))
> > > + continue;
> > > +
> > > + /*
> > > + * Format: .klp.rela.sec_objname.section_name
> > > + * See comment in klp_resolve_symbols() for an explanation
> > > + * of the selected field width value.
> > > + */
> > > + secname = pmod->klp_info->secstrings + sec->sh_name;
> > > + cnt = sscanf(secname, ".klp.rela.%55[^.]", sec_objname);
> > > + if (cnt != 1) {
> > > + pr_err("section %s has an incorrectly formatted name\n",
> > > + secname);
> > > + continue;
> > > + }
>
> Actually, I think we don't need the cnt check here. Once it is removed,
> there isn't much duplicated logic.
Because it must have passed the check once already during
klp_apply_section_relocs()? Yes, perhaps.
Miroslav
next prev parent reply other threads:[~2022-12-09 12:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220901171252.2148348-1-song@kernel.org>
2022-11-17 22:06 ` [PATCH v6] livepatch: Clear relocation targets on a module removal Song Liu
2022-11-18 16:24 ` Petr Mladek
2022-11-18 17:14 ` Song Liu
2022-11-21 15:32 ` Joe Lawrence
2022-11-21 16:32 ` Song Liu
2022-11-29 1:57 ` Song Liu
2022-12-09 11:41 ` powerpc-part: was: " Petr Mladek
2022-12-09 19:59 ` Song Liu
2022-12-12 17:11 ` Petr Mladek
2022-12-12 22:22 ` Song Liu
2022-12-13 8:13 ` Song Liu
2022-12-13 13:29 ` Petr Mladek
2022-12-13 22:19 ` Joe Lawrence
2022-12-13 19:31 ` Song Liu
2022-12-09 12:36 ` x86 part: " Petr Mladek
2022-12-09 12:49 ` Miroslav Benes [this message]
2022-12-09 13:54 ` Petr Mladek
2022-12-09 14:20 ` Petr Mladek
2022-12-09 18:21 ` Song Liu
2022-12-09 12:55 ` Miroslav Benes
2022-12-09 18:30 ` Song Liu
2022-12-09 18:51 ` Christophe Leroy
2022-12-09 19:24 ` Song Liu
2022-12-12 8:16 ` Miroslav Benes
2022-12-13 8:28 ` Song Liu
2022-12-13 14:37 ` Petr Mladek
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.2212091348090.18933@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=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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