[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lgzleb8t.fsf@rustcorp.com.au>
Date: Thu, 25 Aug 2016 13:44:10 +0930
From: Rusty Russell <rusty@...tcorp.com.au>
To: Jiri Kosina <jikos@...nel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Jessica Yu <jeyu@...hat.com>, Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>, linux-kernel@...r.kernel.org,
live-patching@...r.kernel.org, Chunyu Hu <chuhu@...hat.com>
Subject: Re: [PATCH] livepatch/module: make TAINT_LIVEPATCH module-specific
Jiri Kosina <jikos@...nel.org> 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/<klp 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 <chuhu@...hat.com>
>> Signed-off-by: Josh Poimboeuf <jpoimboe@...hat.com>
>
> 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 <rusty@...tcorp.com.au>
Thanks,
Rusty.
Powered by blists - more mailing lists