From: Petr Mladek <pmladek@suse.com>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: live-patching@vger.kernel.org, jpoimboe@redhat.com,
mbenes@suse.cz, nstange@suse.de
Subject: Re: [PATCH 1/4] livepatch/shadow: Separate code to get or use pre-allocated shadow variable
Date: Fri, 29 Jul 2022 17:06:52 +0200 [thread overview]
Message-ID: <YuP3jBVZIdxBm/E/@alley> (raw)
In-Reply-To: <20220701194817.24655-2-mpdesouza@suse.com>
On Fri 2022-07-01 16:48:14, Marcos Paulo de Souza wrote:
> From: Petr Mladek <pmladek@suse.com>
>
> Separate code that is used in klp_shadow_get_or_alloc() under klp_mutex.
> It splits a long spaghetti function into two. Also it unifies the error
> handling. The old used a mix of duplicated code, direct returns,
> and goto. The new code has only one unlock, free, and return calls.
>
> Background: The change was needed by an earlier variant of the code adding
> garbage collection of shadow variables. It is not needed in
> the end. But the change still looks like an useful clean up.
Maybe the above paragraph is superfluous. I would remove it after all.
> It is code refactoring without any functional changes.
>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
(It is fun to review my own RFC patch).
> ---
> kernel/livepatch/shadow.c | 77 ++++++++++++++++++++++-----------------
> 1 file changed, 43 insertions(+), 34 deletions(-)
>
> diff --git a/kernel/livepatch/shadow.c b/kernel/livepatch/shadow.c
> index c2e724d97ddf..67c1313f6831 100644
> --- a/kernel/livepatch/shadow.c
> +++ b/kernel/livepatch/shadow.c
> @@ -101,41 +101,19 @@ void *klp_shadow_get(void *obj, unsigned long id)
> }
> EXPORT_SYMBOL_GPL(klp_shadow_get);
>
> -static void *__klp_shadow_get_or_alloc(void *obj, unsigned long id,
> - size_t size, gfp_t gfp_flags,
> - klp_shadow_ctor_t ctor, void *ctor_data,
> - bool warn_on_exist)
> +static void *__klp_shadow_get_or_use(void *obj, unsigned long id,
> + struct klp_shadow *new_shadow,
> + klp_shadow_ctor_t ctor, void *ctor_data,
> + bool *exist)
I have to admit that the name is a bit misleading. The real meaning
is "get existing" or "use newly allocated one".
I think that the following might better describe the real meaning
in the context where it is used:
__klp_shadow_get_or_alloc_locked()
__klp_shadow_get_or_add()
Anyway, it would deserve some comment above the function definition.
For example:
/*
* Check if the variable already exists. Otherwise, add
* the pre-allocated one.
*/
> {
> - struct klp_shadow *new_shadow;
> void *shadow_data;
> - unsigned long flags;
It would deserve:
lockdep_assert_held(&klp_shadow_lock);
> -
> - /* Check if the shadow variable already exists */
> - shadow_data = klp_shadow_get(obj, id);
> - if (shadow_data)
> - goto exists;
> -
Best Regards,
Petr
next prev parent reply other threads:[~2022-07-29 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 19:48 [PATCH 0/4] livepatch: Add garbage collection for shadow variables Marcos Paulo de Souza
2022-07-01 19:48 ` [PATCH 1/4] livepatch/shadow: Separate code to get or use pre-allocated shadow variable Marcos Paulo de Souza
2022-07-01 21:01 ` Josh Poimboeuf
2022-07-29 15:06 ` Petr Mladek [this message]
2022-07-01 19:48 ` [PATCH 2/4] livepatch/shadow: Separate code removing all shadow variables for a given id Marcos Paulo de Souza
2022-07-29 15:09 ` Petr Mladek
2022-07-01 19:48 ` [PATCH 3/4] livepatch/shadow: Introduce klp_shadow_type structure Marcos Paulo de Souza
2022-07-01 21:04 ` Josh Poimboeuf
2022-07-29 16:07 ` Petr Mladek
2022-08-25 14:50 ` Joe Lawrence
2022-08-25 14:54 ` Joe Lawrence
2022-10-24 13:24 ` Petr Mladek
2022-10-24 12:59 ` Petr Mladek
2022-07-01 19:48 ` [PATCH 4/4] livepatch/shadow: Add garbage collection of shadow variables Marcos Paulo de Souza
2022-08-25 12:59 ` Petr Mladek
2022-08-25 16:26 ` Joe Lawrence
2022-10-24 15:09 ` Petr Mladek
2022-11-01 11:02 ` Petr Mladek
2022-11-02 12:51 ` Joe Lawrence
2022-11-04 14:44 ` Joe Lawrence
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=YuP3jBVZIdxBm/E/@alley \
--to=pmladek@suse.com \
--cc=jpoimboe@redhat.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=nstange@suse.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