From: Jiri Kosina <jikos@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Miroslav Benes <mbenes@suse.cz>,
jpoimboe@redhat.com, jeyu@kernel.org, pmladek@suse.com,
lpechacek@suse.cz, live-patching@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] livepatch: force transition process to finish
Date: Mon, 6 Nov 2017 13:03:32 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.1711061259040.6470@cbobk.fhfr.pm> (raw)
In-Reply-To: <20171106111105.GC24863@amd>
On Mon, 6 Nov 2017, Pavel Machek wrote:
> NAK. Admin does not have chance to decide if this is safe or not.
The process that is actually being suggested here (and towards which the
implementation is heading) is that in case of the convergence being stuck
for unknown reason, the admin of the system collects all the necessary
data (namely stacktraces of the relevant tasks), and requests a clearance
from the livepatch distributor to force the transition.
But I agree with you that this might not be completely clear from the
documentation, and should be made more explicit.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2017-11-06 12:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 11:48 [PATCH v3 0/2] livepatch: Introduce signal and force sysfs attributes Miroslav Benes
2017-10-31 11:48 ` [PATCH v3 1/2] livepatch: send a fake signal to all blocking tasks Miroslav Benes
2017-11-01 15:06 ` Miroslav Benes
2017-11-01 15:13 ` Petr Mladek
2017-11-01 16:43 ` Oleg Nesterov
2017-11-02 10:36 ` Miroslav Benes
2017-11-02 14:08 ` Oleg Nesterov
2017-11-02 13:09 ` Josh Poimboeuf
2017-11-03 8:02 ` Miroslav Benes
2017-11-03 12:57 ` Josh Poimboeuf
2017-11-02 13:32 ` Josh Poimboeuf
2017-11-03 8:06 ` Miroslav Benes
2017-11-06 11:08 ` Pavel Machek
2017-10-31 11:48 ` [PATCH v3 2/2] livepatch: force transition process to finish Miroslav Benes
2017-11-01 15:32 ` Petr Mladek
2017-11-02 13:13 ` Josh Poimboeuf
2017-11-03 8:07 ` Miroslav Benes
2017-11-06 11:11 ` Pavel Machek
2017-11-06 12:03 ` Jiri Kosina [this message]
2017-11-09 11:14 ` Pavel Machek
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=nycvar.YFH.7.76.1711061259040.6470@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=jeyu@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lpechacek@suse.cz \
--cc=mbenes@suse.cz \
--cc=pavel@ucw.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;
as well as URLs for NNTP newsgroup(s).