Live Patching
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Chengming Zhou <zhouchengming@bytedance.com>,
	jpoimboe@redhat.com, jikos@kernel.org, joe.lawrence@redhat.com,
	live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	songmuchun@bytedance.com, qirui.001@bytedance.com
Subject: Re: [PATCH v3] livepatch: Don't block removal of patches that are safe to unload
Date: Wed, 16 Mar 2022 16:01:02 +0100	[thread overview]
Message-ID: <YjH7rniD4rBO6JIP@alley> (raw)
In-Reply-To: <alpine.LSU.2.21.2203161536330.6444@pobox.suse.cz>

On Wed 2022-03-16 15:48:25, Miroslav Benes wrote:
> On Sat, 12 Mar 2022, Chengming Zhou wrote:
> 
> > module_put() is not called for a patch with "forced" flag. It should
> > block the removal of the livepatch module when the code might still
> > be in use after forced transition.
> > 
> > klp_force_transition() currently sets "forced" flag for all patches on
> > the list.
> > 
> > In fact, any patch can be safely unloaded when it passed through
> > the consistency model in KLP_UNPATCHED transition.
> > 
> > By other words, the "forced" flag must be set only for livepatches
> 
> s/By/In/
> 
> > that are being removed. In particular, set the "forced" flag:
> > 
> >   + only for klp_transition_patch when the transition to KLP_UNPATCHED
> >     state was forced.
> > 
> >   + all replaced patches when the transition to KLP_PATCHED state was
> >     forced and the patch was replacing the existing patches.
> > 
> > index 5683ac0d2566..7f25a5ae89f6 100644
> > --- a/kernel/livepatch/transition.c
> > +++ b/kernel/livepatch/transition.c
> > @@ -641,6 +641,18 @@ void klp_force_transition(void)
> >  	for_each_possible_cpu(cpu)
> >  		klp_update_patch_state(idle_task(cpu));
> >  
> > -	klp_for_each_patch(patch)
> > -		patch->forced = true;
> > +	/*
> > +	 * Only need to set forced flag for the transition patch
> > +	 * when force transition to KLP_UNPATCHED state, but
> > +	 * have to set forced flag for all replaced patches
> > +	 * when force atomic replace transition.
> > +	 */
> 
> How about something like
> 
> /*
>  * Set forced flag for patches being removed, which is the transition
>  * patch in KLP_UNPATCHED state or all replaced patches when forcing
>  * the atomic replace transition.
>  */

Or just the first sentence:

	/* Set forced flag for patches being removed */

The rest is visible from the code.

Either version works for me. If we agree on it then I update
the text when pushing the patch.

Best Regards,
Petr

  reply	other threads:[~2022-03-16 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12 15:22 [PATCH v3] livepatch: Don't block removal of patches that are safe to unload Chengming Zhou
2022-03-16 14:48 ` Miroslav Benes
2022-03-16 15:01   ` Petr Mladek [this message]
2022-03-16 15:03     ` Miroslav Benes
2022-03-17  1:43       ` Joe Lawrence
2022-03-17  1:15     ` [External] " Chengming Zhou
2022-03-16 14:55 ` Petr Mladek
2022-03-17 18:38 ` 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=YjH7rniD4rBO6JIP@alley \
    --to=pmladek@suse.com \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=qirui.001@bytedance.com \
    --cc=songmuchun@bytedance.com \
    --cc=zhouchengming@bytedance.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