Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3119692yba; Mon, 6 May 2019 17:43:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqzqNTHTk8jUmByYN2guhLyU52e2hw/BWIAav0d5q3UhbbKvNtRkwhz9rRMdLZW3/oOmI2ui X-Received: by 2002:a63:db55:: with SMTP id x21mr34653756pgi.219.1557189790229; Mon, 06 May 2019 17:43:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557189790; cv=none; d=google.com; s=arc-20160816; b=b4wOQz90Jgus+d4U9zFR/EuH7eIONxFg9St6u0a6h38K4Rw4lGgtbKMfefnZs35c+p +B04ylaEjN69cW2TOFOs1QvJe8VUR11CJ38mP7czjRplV3a7EvPrCWr6MeSUP9kHWW95 j/msqI4HxkwNCgAF3d9E/K6hqvKVgJoFsXqzsUmFwuTIZ7vc4VE1eHcVel1TB5ZTASKC 4S3MZrzZpUF7ZFSKtzM/tNXPrbtZBx2SVnsUweJkx1IvoOudcilvm1781SHlrgsGMFTF SR8BVsl2s2Cjt+kJH8mSWhbIngGeFIAN6xzYg4nFZEGJtDg9Fx2M+xp6mTZBCx3IJ8Iw N7Sg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=lmQOFpBaUFYz4dfO26ArhwxD5tWiX3uvzTaoq8TeE0A=; b=Y5C5K3OH87n5nIEWUwUk1sgrUrvxRJBZ3fmh7eIiBr6I9mYCCvZ7NYgJwJzWUofZUz 1ziN6sywadmsZnGgDsjbE2CpmqIlfhGFxsntvyZ+TxugmkuyfjWV8tlWBNegk36nLwDo U2j5As/029zRRpBBG8fl26ILMFAVkXux30d8FU60a2pLyPjAZ70OcDJ1MZUpxS5CHUFU 5B63ncrheHuKTYVRg/dUPO8s9xfzHRUtmkuWpv1814kBsZezc76L0TD7NzF8xESZqL9n WWyGKa09/YLDycES7hav2zzq/7/83Z6IXbDE4hLc42gBj5vWFuZ5NirB6DcpH7IDiDSD qWWQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e26si16293949pfi.54.2019.05.06.17.42.54; Mon, 06 May 2019 17:43:10 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726489AbfEGAkj (ORCPT + 99 others); Mon, 6 May 2019 20:40:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48104 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726073AbfEGAkj (ORCPT ); Mon, 6 May 2019 20:40:39 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F02F859468; Tue, 7 May 2019 00:40:38 +0000 (UTC) Received: from treble (ovpn-123-166.rdu2.redhat.com [10.10.123.166]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 403B1611CF; Tue, 7 May 2019 00:40:34 +0000 (UTC) Date: Mon, 6 May 2019 19:40:32 -0500 From: Josh Poimboeuf To: Petr Mladek Cc: Jiri Kosina , Miroslav Benes , 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 Message-ID: <20190507004032.2fgddlsycyypqdsn@treble> References: <20190430091049.30413-1-pmladek@suse.com> <20190430091049.30413-2-pmladek@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190430091049.30413-2-pmladek@suse.com> User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Tue, 07 May 2019 00:40:39 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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; ret = save_stack_trace_tsk_reliable(task, &trace); [ no need to check ret for ENOSYS here ] Then, IMO, no comment is needed. -- Josh