From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752576AbdKFMDf (ORCPT ); Mon, 6 Nov 2017 07:03:35 -0500 Received: from mx2.suse.de ([195.135.220.15]:57963 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752340AbdKFMDe (ORCPT ); Mon, 6 Nov 2017 07:03:34 -0500 Date: Mon, 6 Nov 2017 13:03:32 +0100 (CET) From: Jiri Kosina To: Pavel Machek cc: Miroslav Benes , 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 In-Reply-To: <20171106111105.GC24863@amd> Message-ID: References: <20171031114853.841-1-mbenes@suse.cz> <20171031114853.841-3-mbenes@suse.cz> <20171106111105.GC24863@amd> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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