From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756775AbcHXVnP (ORCPT ); Wed, 24 Aug 2016 17:43:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58702 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755689AbcHXVnM (ORCPT ); Wed, 24 Aug 2016 17:43:12 -0400 Date: Wed, 24 Aug 2016 16:43:02 -0500 From: Josh Poimboeuf To: Jessica Yu , Jiri Kosina , Miroslav Benes Cc: 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 Message-ID: <20160824214302.4pogu4lwi2i2cgnn@treble> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 24 Aug 2016 21:43:04 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 24, 2016 at 04:33:00PM -0500, 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 "the the" -> "the" > module is loaded, rather than when it's enabled. > > Reviewed-by: Chunyu Hu > Signed-off-by: Josh Poimboeuf -- Josh