lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 6 Nov 2017 13:03:32 +0100 (CET)
From:   Jiri Kosina <jikos@...nel.org>
To:     Pavel Machek <pavel@....cz>
cc:     Miroslav Benes <mbenes@...e.cz>, jpoimboe@...hat.com,
        jeyu@...nel.org, pmladek@...e.com, lpechacek@...e.cz,
        live-patching@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/2] livepatch: force transition process to finish

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

Powered by blists - more mailing lists