From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Yafang Shao <laoar.shao@gmail.com>,
jikos@kernel.org, mbenes@suse.cz, joe.lawrence@redhat.com,
live-patching@vger.kernel.org
Subject: Re: [PATCH 2/3] livepatch: Avoid blocking tasklist_lock too long
Date: Wed, 12 Feb 2025 17:36:03 -0800 [thread overview]
Message-ID: <20250213013603.i6uxtjvc3qxlsqwc@jpoimboe> (raw)
In-Reply-To: <Z6zBb9GRkFC-R0RE@pathway.suse.cz>
On Wed, Feb 12, 2025 at 04:42:39PM +0100, Petr Mladek wrote:
> CPU1 CPU1
>
> klp_try_complete_transition()
>
>
> taskA:
> + fork()
> + klp_copy_process()
> child->patch_state = KLP_PATCH_UNPATCHED
>
> klp_try_switch_task(taskA)
> // safe
>
> child->patch_state = KLP_PATCH_PATCHED
>
> all processes patched
>
> klp_finish_transition()
>
>
> list_add_tail_rcu(&p->thread_node,
> &p->signal->thread_head);
>
>
> BANG: The forked task has KLP_PATCH_UNPATCHED so that
> klp_ftrace_handler() will redirect it to the old code.
>
> But CPU1 thinks that all tasks are migrated and is going
> to finish the transition
Maybe klp_try_complete_transition() could iterate the tasks in two
passes? The first pass would use rcu_read_lock(). Then if all tasks
appear to be patched, try again with tasklist_lock.
Or, we could do something completely different. There's no need for
klp_copy_process() to copy the parent's state: a newly forked task can
be patched immediately because it has no stack.
So instead, just initialize it to KLP_TRANSITION_IDLE with
TIF_PATCH_PENDING cleared. Then when klp_ftrace_handler() encounters a
KLP_TRANSITION_IDLE task, it considers its state to be 'klp_target_state'.
// called from copy_process()
void klp_init_task(struct task_struct *child)
{
/* klp_ftrace_handler() will transition the task immediately */
child->patch_state = KLP_TRANSITION_IDLE;
clear_tsk_thread_flag(child, TIF_PATCH_PENDING);
}
klp_ftrace_handler():
patch_state = current->patch_state;
if (patch_state == KLP_TRANSITION_IDLE)
patch_state = klp_target_state;
...
Hm?
> I would first like to understand how exactly the stall happens.
> It is possible that even rcu_read_lock() won't help here!
>
> If the it takes too long time to check backtraces of all pending
> processes then even rcu_read_lock() might trigger the RCU stall
> warning as well.
Yeah, based on Yafang's reply it appears there are RCU stalls either
way.
--
Josh
next prev parent reply other threads:[~2025-02-13 1:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 6:24 [PATCH 0/3] livepatch: Some improvements Yafang Shao
2025-02-11 6:24 ` [PATCH 1/3] livepatch: Add comment to clarify klp_add_nops() Yafang Shao
2025-02-12 12:51 ` Petr Mladek
2025-02-13 5:49 ` Yafang Shao
2025-02-11 6:24 ` [PATCH 2/3] livepatch: Avoid blocking tasklist_lock too long Yafang Shao
2025-02-12 0:40 ` Josh Poimboeuf
2025-02-12 2:34 ` Yafang Shao
2025-02-12 11:54 ` Yafang Shao
2025-02-12 15:42 ` Petr Mladek
2025-02-13 1:36 ` Josh Poimboeuf [this message]
2025-02-13 5:53 ` Yafang Shao
2025-02-13 9:48 ` Petr Mladek
2025-02-13 17:32 ` Josh Poimboeuf
2025-02-14 14:44 ` Petr Mladek
2025-02-14 18:12 ` Josh Poimboeuf
2025-02-18 2:37 ` Yafang Shao
2025-02-13 2:47 ` Josh Poimboeuf
2025-02-13 11:19 ` Find root of the stall: was: " Petr Mladek
2025-02-13 12:32 ` Yafang Shao
2025-02-13 12:39 ` Yafang Shao
2025-02-14 2:44 ` Yafang Shao
2025-02-14 8:36 ` Josh Poimboeuf
2025-02-14 11:37 ` Petr Mladek
2025-02-18 2:19 ` Yafang Shao
2025-02-14 9:46 ` Petr Mladek
2025-02-11 6:24 ` [PATCH 3/3] livepatch: Avoid potential RCU stalls in klp transition Yafang Shao
2025-02-12 0:52 ` Josh Poimboeuf
2025-02-12 2:42 ` Yafang Shao
2025-02-13 1:58 ` Josh Poimboeuf
2025-02-13 5:51 ` Yafang Shao
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=20250213013603.i6uxtjvc3qxlsqwc@jpoimboe \
--to=jpoimboe@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=laoar.shao@gmail.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.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