Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751836AbbBUUxh (ORCPT ); Sat, 21 Feb 2015 15:53:37 -0500 Received: from cantor2.suse.de ([195.135.220.15]:50275 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751718AbbBUUxg (ORCPT ); Sat, 21 Feb 2015 15:53:36 -0500 Date: Sat, 21 Feb 2015 21:53:33 +0100 (CET) From: Jiri Kosina To: Ingo Molnar cc: Vojtech Pavlik , Josh Poimboeuf , Peter Zijlstra , Andrew Morton , Ingo Molnar , Seth Jennings , linux-kernel@vger.kernel.org, Linus Torvalds Subject: Re: live patching design (was: Re: [PATCH 1/3] sched: add sched_task_call()) In-Reply-To: Message-ID: References: <20150220095003.GA23506@gmail.com> <20150220104418.GD25076@gmail.com> <20150220194901.GB3603@gmail.com> <20150220214613.GA21598@suse.com> <20150221181852.GA8406@gmail.com> <20150221191607.GA9534@gmail.com> <20150221194840.GA10126@gmail.com> 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 Content-Length: 1287 Lines: 30 To make sure that this thread doesn't conclude in void, here's my take on it: - what's currently alredy there is the simplest-of-simplest methods; it allows you to apply context-less patches (such as adding bounds checking to the beginning of syscall, etc), which turns out to cover vast portion of applicable CVEs - it can always be made more clever; patch author always has to know the version of the kernel he's preparing the patch for anyway (the live patch and the kernel is closely tied together) - the proposal to force sleeping or CPU-hogging tasks through a defined safe checkpoint using a fake sort-of signal without any other sideeffects might be useful even for kGraft and also for other proposed aproaches. I think we'll try to implement this as an optimization for kGraft and we'll see how (a) fast (b) non-intrusive we would be able to make it. If it turns out to be successful, we can then just reuse it in the upstream solution (whatever that would be) Thanks, -- Jiri Kosina SUSE Labs -- 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/