From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758285AbcHYLcb (ORCPT ); Thu, 25 Aug 2016 07:32:31 -0400 Received: from ozlabs.org ([103.22.144.67]:58566 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751675AbcHYLca (ORCPT ); Thu, 25 Aug 2016 07:32:30 -0400 From: Rusty Russell To: Jiri Kosina , Josh Poimboeuf Cc: Jessica Yu , Miroslav Benes , Petr Mladek , linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, Chunyu Hu Subject: Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific In-Reply-To: References: User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Thu, 25 Aug 2016 13:44:10 +0930 Message-ID: <87lgzleb8t.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jiri Kosina writes: > 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 Happy to leave it to you :) Acked-by: Rusty Russell Thanks, Rusty.