Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp10427679imu; Thu, 6 Dec 2018 00:30:56 -0800 (PST) X-Google-Smtp-Source: AFSGD/VaumtgaSeg+Kp9wJftgqXYl6zF3/9x0ZgBMRxgjuKBqBwLGTN22XQr8ZPaXX0P3hvr9NOy X-Received: by 2002:a17:902:2a66:: with SMTP id i93mr26867432plb.113.1544085056141; Thu, 06 Dec 2018 00:30:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544085056; cv=none; d=google.com; s=arc-20160816; b=FpkCMa1lX/XgTDTrkXpMSwD4q2DIqv36hNIk/0VjI0a61DJln4Gtm/iVshFvl+Zq/f o7sseW6VkshW9hEvuPRqKCdeSmvxnP3sBKJY8d0cSD8qqm14tVj0pKyivvcfQaTtW4q6 QKEFNl2FtS5H2dxsyntTPsCucgHLKbHd6PJ2yA7AZyuAPCneMIEKOtY00SLCtOiDkoiA nhcjo2QwXx1lClS29aYVLGFjRJXFJ34ccMWcfRv4DRZ1mmae+n7/CiYEVZo9tGLdNsKO gCSvOLkbiw2W35ECk9miUlU2xJVj3VV5OVN672sYdeO4joYYdiE3KpGxw3ZA9UKlSode D1ZQ== 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=7FVZ3FU39/Wp75rTicL47GBRuDh1mwCqJb2/3K+vBCU=; b=XXeEDvLPxgaB7HBKpV6IFKOFccyuhxTrDiKunozofan+k+lRpXe2ubnrKvIYQO4oMo qwGl4e5zAlIgLnsy7eCXlEzTXTlhZbKa131a5djpW6B9rTgFiC5hdcP4DNwqhUgALQKc icnoBd393eKYSJ45KvU8VQ3/PNewE3Wfi+4zZtqHwlx8ceiq/gNV8nLaqYMC/ghmFwEx w/axiWvOwebyYOkELWe6zEBeH44dgWfh/SKCZWXrF3UW0hXYX2dljVFHCGcZrCKSk8OG GbRnl+ReJ0Z+JUOk8A1dcWbNwym7sfMBJcDIT2arEfZ5zfyJNQdaOmiqgCPEEy1bYwd7 3adA== 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 a23si22886978plm.334.2018.12.06.00.30.40; Thu, 06 Dec 2018 00:30:56 -0800 (PST) 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 S1729127AbeLFI2R (ORCPT + 99 others); Thu, 6 Dec 2018 03:28:17 -0500 Received: from mx2.suse.de ([195.135.220.15]:43438 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727575AbeLFI2R (ORCPT ); Thu, 6 Dec 2018 03:28:17 -0500 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 399FDAD75; Thu, 6 Dec 2018 08:28:15 +0000 (UTC) Date: Thu, 6 Dec 2018 09:28:14 +0100 From: Petr Mladek To: Joe Lawrence Cc: Jiri Kosina , Josh Poimboeuf , Miroslav Benes , Jason Baron , Evgenii Shatokhin , live-patching@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v14 05/11] livepatch: Simplify API by removing registration step Message-ID: <20181206082814.uyzjw2q4avknhswd@pathway.suse.cz> References: <20181129094431.7801-1-pmladek@suse.com> <20181129094431.7801-6-pmladek@suse.com> <20181205193253.mhlqj37r4o6ukkhp@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181205193253.mhlqj37r4o6ukkhp@redhat.com> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 2018-12-05 14:32:53, Joe Lawrence wrote: > > diff --git a/kernel/livepatch/core.c b/kernel/livepatch/core.c > > index 972520144713..e01dfa3b58d2 100644 > > --- a/kernel/livepatch/core.c > > +++ b/kernel/livepatch/core.c > > @@ -45,7 +45,7 @@ > > */ > > DEFINE_MUTEX(klp_mutex); > > > > -/* Registered patches */ > > +/* Actively used patches. */ > > LIST_HEAD(klp_patches); > > By itself, this comment makes me wonder if there are un-active and/or > un-used patches that I need to worry about. After this patchset, > klp_patches will include patches that have been enabled and those that > have been replaced, but the replacement transition is still in progress. > > If that sounds accurate, how about adding to the comment: > > /* Actively used patches: enabled or replaced and awaiting transition */ The replaced patches are not in the list. This is why I used the word "actively". /* * Actively used patches: enabled or in transition. Note that replaced * or disabled patches are not listed even though the related kernel * module still can be loaded. */ Best Regards, Petr