From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Seth Forshee <sforshee@kernel.org>,
Peter Zijlstra <peterz@infradead.org>, Song Liu <song@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Miroslav Benes <mbenes@suse.cz>, Jiri Kosina <jikos@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH v2 2/3] livepatch,sched: Add livepatch task switching to cond_resched()
Date: Wed, 22 Feb 2023 15:00:33 +0100 [thread overview]
Message-ID: <Y/YgARbqsyvzebAl@alley> (raw)
In-Reply-To: <9f09bff809fc026618108e8bbaac67ef2f8e6d3d.1676672328.git.jpoimboe@kernel.org>
On Fri 2023-02-17 14:22:55, Josh Poimboeuf wrote:
> There have been reports [1][2] of live patches failing to complete
> within a reasonable amount of time due to CPU-bound kthreads.
>
> Fix it by patching tasks in cond_resched().
>
> There are four different flavors of cond_resched(), depending on the
> kernel configuration. Hook into all of them.
>
> A more elegant solution might be to use a preempt notifier. However,
> non-ORC unwinders can't unwind a preempted task reliably.
>
> [1] https://lore.kernel.org/lkml/20220507174628.2086373-1-song@kernel.org/
> [2] https://lkml.kernel.org/lkml/20230120-vhost-klp-switching-v1-0-7c2b65519c43@kernel.org
>
> --- a/kernel/livepatch/transition.c
> +++ b/kernel/livepatch/transition.c
> @@ -588,14 +641,10 @@ void klp_reverse_transition(void)
> klp_target_state == KLP_PATCHED ? "patching to unpatching" :
> "unpatching to patching");
>
> - klp_transition_patch->enabled = !klp_transition_patch->enabled;
> -
> - klp_target_state = !klp_target_state;
> -
> /*
> * Clear all TIF_PATCH_PENDING flags to prevent races caused by
> - * klp_update_patch_state() running in parallel with
> - * klp_start_transition().
> + * klp_update_patch_state() or __klp_sched_try_switch() running in
> + * parallel with the reverse transition.
> */
> read_lock(&tasklist_lock);
> for_each_process_thread(g, task)
> @@ -605,9 +654,16 @@ void klp_reverse_transition(void)
> for_each_possible_cpu(cpu)
> clear_tsk_thread_flag(idle_task(cpu), TIF_PATCH_PENDING);
>
> - /* Let any remaining calls to klp_update_patch_state() complete */
> + /*
> + * Make sure all existing invocations of klp_update_patch_state() and
> + * __klp_sched_try_switch() see the cleared TIF_PATCH_PENDING before
> + * starting the reverse transition.
> + */
> klp_synchronize_transition();
>
> + /* All patching has stopped, now start the reverse transition. */
> + klp_transition_patch->enabled = !klp_transition_patch->enabled;
> + klp_target_state = !klp_target_state;
I have double checked the synchronization and we need here:
/*
* Make sure klp_update_patch_state() and __klp_sched_try_switch()
* see the updated klp_target_state before TIF_PATCH_PENDING
* is set again in klp_start_transition().
*/
smp_wmb();
The same is achieved by smp_wmb() in klp_init_transition().
Note that the extra barrier was missing here because klp_target_state
was set before klp_synchronize_transition(). It was fine because
klp_update_patch_state() was called on locations where a transition
in any direction was always safe.
Just for record. We need to modify @klp_target_state after
klp_synchronize_transition() now. The value is used by
__klp_sched_try_switch() to decide when the transition
is safe. It defines what functions must not be on the stack.
I am sorry that I missed this when reviewing v1. I think that I needed
to see the new code with a fresh head.
> klp_start_transition();
> }
I do not see any other problem. With the above barrier added,
feel free to use:
Reviewed-by: Petr Mladek <pmladek@suse.com>
It is for the livepatching part. I checked also the scheduler
code and it looked fine but I would not put my hand in the fire
for it.
Best Regards,
Petr
next prev parent reply other threads:[~2023-02-22 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 22:22 [PATCH v2 0/3] livepatch,sched: Add livepatch task switching to cond_resched() Josh Poimboeuf
2023-02-17 22:22 ` [PATCH v2 1/3] livepatch: Skip task_call_func() for current task Josh Poimboeuf
2023-02-17 22:22 ` [PATCH v2 2/3] livepatch,sched: Add livepatch task switching to cond_resched() Josh Poimboeuf
2023-02-22 14:00 ` Petr Mladek [this message]
2023-02-24 1:34 ` Josh Poimboeuf
2023-02-24 16:01 ` Petr Mladek
2023-02-24 16:42 ` Josh Poimboeuf
2023-02-17 22:22 ` [PATCH v2 3/3] vhost: Fix livepatch timeouts in vhost_worker() Josh Poimboeuf
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=Y/YgARbqsyvzebAl@alley \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sforshee@kernel.org \
--cc=song@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