From: zhang warden <zhangwarden@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Yafang Shao <laoar.shao@gmail.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
mbenes@suse.cz, joe.lawrence@redhat.com,
live-patching@vger.kernel.org
Subject: Re: [PATCH] livepatch: Avoid hard lockup caused by klp_try_switch_task()
Date: Sat, 1 Feb 2025 10:04:32 +0800 [thread overview]
Message-ID: <86736F95-020D-476F-999C-8666A6B0BC23@gmail.com> (raw)
In-Reply-To: <Z5zSmlRIv5qhuVja@pathway.suse.cz>
> On Jan 31, 2025, at 21:39, Petr Mladek <pmladek@suse.com> wrote:
>
> You got it right. I am afraid that it might create a livelock
> situation for the livepatch transition. I mean that the check
> might almost always break on systems with thousands of processes
> and frequently created/exited processes. It always has
> to start from the beginning.
>
> Best Regards,
> Petr
True. It will easily raise the problem that some important process cannot successfully finish the target patch state and make the livepatch-fix unable to work on some key process(which may happen).
If this happens, I am sure it would be a nightmare...
Best Regards,
Wardenjohn
next prev parent reply other threads:[~2025-02-01 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 8:51 [PATCH] livepatch: Avoid hard lockup caused by klp_try_switch_task() Yafang Shao
2025-01-22 12:50 ` Petr Mladek
2025-01-22 13:46 ` Yafang Shao
2025-01-31 13:06 ` Miroslav Benes
2025-01-31 13:22 ` zhang warden
2025-01-31 13:39 ` Petr Mladek
2025-02-01 2:04 ` zhang warden [this message]
2025-02-05 8:39 ` Yafang Shao
2025-02-06 16:43 ` Petr Mladek
2025-02-07 2:16 ` 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=86736F95-020D-476F-999C-8666A6B0BC23@gmail.com \
--to=zhangwarden@gmail.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--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