From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754598AbcHYEpA (ORCPT ); Thu, 25 Aug 2016 00:45:00 -0400 Received: from mx2.suse.de ([195.135.220.15]:50939 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753369AbcHYEnp (ORCPT ); Thu, 25 Aug 2016 00:43:45 -0400 Date: Thu, 25 Aug 2016 02:54:21 +0200 (CEST) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: Josh Poimboeuf cc: Jessica Yu , Miroslav Benes , Petr Mladek , linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, Chunyu Hu , Rusty Russell Subject: Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) 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 Wed, 24 Aug 2016, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module//taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty party is by converting > CONFIG_LIVEPATCH to a module taint flag. > > This changes the behavior a bit: now the the flag gets set when the > module is loaded, rather than when it's enabled. > > Reviewed-by: Chunyu Hu > Signed-off-by: Josh Poimboeuf I like this change. Rusty, in case you're okay with it as well, could you please either provide your Ack so that I could take it through livepatching.git? Alternatively, if you prefer to merge this through your tree, please feel free to add Acked-by: Jiri Kosina Thanks, -- Jiri Kosina SUSE Labs