Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751578AbaLQDna (ORCPT ); Tue, 16 Dec 2014 22:43:30 -0500 Received: from mail-yk0-f171.google.com ([209.85.160.171]:57673 "EHLO mail-yk0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751066AbaLQDn3 (ORCPT ); Tue, 16 Dec 2014 22:43:29 -0500 MIME-Version: 1.0 In-Reply-To: References: <1418752700-14649-1-git-send-email-sjenning@redhat.com> Date: Wed, 17 Dec 2014 09:13:28 +0530 Message-ID: Subject: Re: [PATCHv7 0/3] Kernel Live Patching From: Balbir Singh To: Jiri Kosina Cc: Seth Jennings , Josh Poimboeuf , Vojtech Pavlik , Steven Rostedt , Petr Mladek , Miroslav Benes , Christoph Hellwig , Greg KH , Andy Lutomirski , Masami Hiramatsu , live-patching@vger.kernel.org, x86@kernel.org, kpatch@redhat.com, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 17, 2014 at 1:44 AM, Jiri Kosina wrote: > On Tue, 16 Dec 2014, Balbir Singh wrote: > >> Could you describe what this does to signing? I presume the patched >> module should cause a taint on module signing? > > Hmm, why should it? > I wanted to clarify it from a different perspective If the base image is signed by X and the patched module is signed by Y, is that supported. What does it imply in the case of live-patching? Balbir Singh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/