From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: jikos@kernel.org, jeyu@kernel.org, pmladek@suse.com,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] livepatch: Send a fake signal periodically
Date: Mon, 4 Jun 2018 13:03:25 -0500 [thread overview]
Message-ID: <20180604180325.yeewbafxpjkt6gi5@treble> (raw)
In-Reply-To: <20180604141636.11523-2-mbenes@suse.cz>
On Mon, Jun 04, 2018 at 04:16:35PM +0200, Miroslav Benes wrote:
> An administrator may send a fake signal to all remaining blocking tasks
> of a running transition by writing to
> /sys/kernel/livepatch/<patch>/signal attribute. Let's do it
> automatically after 10 seconds. The timeout is chosen deliberately. It
> gives the tasks enough time to transition themselves.
>
> Theoretically, sending it once should be more than enough. Better be safe
> than sorry, so send it periodically.
This is the part I don't understand. Why do it periodically?
Instead, might it make sense to just send the signals once, and if that
doesn't work, reverse the transition? Then we could make patching a
synchronous operation. But then, it might be remotely possible that the
reverse operation also stalls (e.g., on a kthread). So, maybe it's best
to just leave all these controls in the hands of the user.
All that said, a few code review comments:
- AFAICT, it does an 8 second delay instead of a 10 second delay,
because
a) try_complete_transition() is first called before there's any delay;
b) the preincrement operator used on signals_cnt.
- I think 15 seconds might be a better default. I've seen longer
patching delays on a system with 100+ CPUs.
- If a kthread or idle task is sleeping on a patched function, the
pr_notice("signaling remaining tasks\n") will be repeated continously.
- It might be cleaner to do it from the delayed work function
(klp_transition_work_fn).
--
Josh
next prev parent reply other threads:[~2018-06-04 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 14:16 [PATCH 0/2] Periodic fake signal Miroslav Benes
2018-06-04 14:16 ` [PATCH 1/2] livepatch: Send a fake signal periodically Miroslav Benes
2018-06-04 18:03 ` Josh Poimboeuf [this message]
2018-06-05 7:17 ` Miroslav Benes
2018-06-05 14:01 ` Josh Poimboeuf
2018-06-06 7:49 ` Miroslav Benes
2018-06-11 8:45 ` Petr Mladek
2018-06-04 14:16 ` [PATCH 2/2] livepatch: Remove signal sysfs attribute Miroslav Benes
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=20180604180325.yeewbafxpjkt6gi5@treble \
--to=jpoimboe@redhat.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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