Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3490875yba; Tue, 7 May 2019 02:01:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqzCnym9jgWTWdpejCAmCI9DC/wmNqAEHzhXKukk3nOW6Y3NKdnp0JyUUn2VRqHxby9tCNHj X-Received: by 2002:a62:7689:: with SMTP id r131mr40962530pfc.181.1557219687450; Tue, 07 May 2019 02:01:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557219687; cv=none; d=google.com; s=arc-20160816; b=c6eRF89qzpeuq6hldHEH/bEf7i8NpCpB+JCNbRI+wKlxEmhLeSuCnpzatAhU7ltnId N6QOqPHRYPu3t3JOv1d+pRWCbaeKt3V3mgZm611Ze3UvX0ImHt4WO+qL36pbm4IirN+z wrOEOlHevfTL8ay1kJ4gfYIR0dEdLrCgTw2GFinF1RAwTcpUr92FRg1gIgb2vG6G8HIl 4KsE+KjFWSCA/+3me/iZ8QjFQT2cQ2F8r7urThqrDUKNUOPWbSWjUOSoXfx+p2Mos2hZ fwC1x2GYeT3YhGaqiukNL7OQW9UaoqcS3nOsZdpaTyzX5oDggBsAsiws/w/A1gV+Yx3/ AXCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=UANE7sAgnEymEaCIXbJy+jXg2x269rAcBnk/REp3Lco=; b=EOb/Zp7fNaARmcR/cKaOy4I0b4wIBuikMbmNDz34FjrPqdJQzVQnDdL8rSnuMZWDZ7 HmNcpOVS/1u+rKH3bp+CbiMMMRvBaURN88LtXHTN2gEh4RsMh8sPPWpgRDDVAOJnCiRv dLOU/2JJXQbMnIP6JQlLvbT68VxkfFPsjlc1uuOXIW7xyG3myMCEghuE1/II8t05rY/l 6NbqAvUagJRxMo8T2rMoDmXBKpEbu5ErMHS+yt1hCnJpNbAXNL56/rn87l/7PyLTeHZG 2rVRhgMV73fhpJe+8jpXy4i4XM+K9Nc8VBqh7x0tIb8KMx49S/pRBB3dy+pKDaOY2MBV QC8w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u2si17578739pfn.4.2019.05.07.02.01.10; Tue, 07 May 2019 02:01:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbfEGI64 (ORCPT + 99 others); Tue, 7 May 2019 04:58:56 -0400 Received: from mx2.suse.de ([195.135.220.15]:44488 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726331AbfEGI6z (ORCPT ); Tue, 7 May 2019 04:58:55 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 77065ABAC; Tue, 7 May 2019 08:58:54 +0000 (UTC) Date: Tue, 7 May 2019 10:58:53 +0200 (CEST) From: Miroslav Benes To: Josh Poimboeuf cc: Petr Mladek , Jiri Kosina , Joe Lawrence , Kamalesh Babulal , live-patching@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] livepatch: Remove duplicate warning about missing reliable stacktrace support In-Reply-To: <20190507004032.2fgddlsycyypqdsn@treble> Message-ID: References: <20190430091049.30413-1-pmladek@suse.com> <20190430091049.30413-2-pmladek@suse.com> <20190507004032.2fgddlsycyypqdsn@treble> 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 6 May 2019, Josh Poimboeuf wrote: > On Tue, Apr 30, 2019 at 11:10:48AM +0200, Petr Mladek wrote: > > WARN_ON_ONCE() could not be called safely under rq lock because > > of console deadlock issues. Fortunately, there is another check > > for the reliable stacktrace support in klp_enable_patch(). > > > > Signed-off-by: Petr Mladek > > --- > > kernel/livepatch/transition.c | 9 ++++++++- > > 1 file changed, 8 insertions(+), 1 deletion(-) > > > > diff --git a/kernel/livepatch/transition.c b/kernel/livepatch/transition.c > > index 9c89ae8b337a..8e0274075e75 100644 > > --- a/kernel/livepatch/transition.c > > +++ b/kernel/livepatch/transition.c > > @@ -263,8 +263,15 @@ static int klp_check_stack(struct task_struct *task, char *err_buf) > > trace.nr_entries = 0; > > trace.max_entries = MAX_STACK_ENTRIES; > > trace.entries = entries; > > + > > ret = save_stack_trace_tsk_reliable(task, &trace); > > - WARN_ON_ONCE(ret == -ENOSYS); > > + /* > > + * pr_warn() under task rq lock might cause a deadlock. > > + * Fortunately, missing reliable stacktrace support has > > + * already been handled when the livepatch was enabled. > > + */ > > + if (ret == -ENOSYS) > > + return ret; > > I find the comment to be a bit wordy and confusing (and vague). > > Also this check is effectively the same as the klp_have_reliable_stack() > check which is done in kernel/livepatch/core.c. So I think it would be > clearer and more consistent if the same check is done here: > > if (!klp_have_reliable_stack()) > return -ENOSYS; We removed it in 1d98a69e5cef ("livepatch: Remove reliable stacktrace check in klp_try_switch_task()") and I do think it does not belong here. We can check for the facility right at the beginning in klp_enable_patch() and it is not necessary to do it every time klp_check_stack() is called. But it is nothing I could not live with, so if you decide it is better, I will not object. Miroslav