Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752056AbbBVIwn (ORCPT ); Sun, 22 Feb 2015 03:52:43 -0500 Received: from cantor2.suse.de ([195.135.220.15]:39214 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751547AbbBVIwm (ORCPT ); Sun, 22 Feb 2015 03:52:42 -0500 Date: Sun, 22 Feb 2015 09:52:38 +0100 (CET) From: Jiri Kosina To: Ingo Molnar cc: Josh Poimboeuf , Vojtech Pavlik , 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: <20150221183005.GB8406@gmail.com> Message-ID: References: <20150219214229.GD15980@treble.redhat.com> <20150220095003.GA23506@gmail.com> <20150220104418.GD25076@gmail.com> <20150220194901.GB3603@gmail.com> <20150220214613.GA21598@suse.com> <20150220220845.GI15980@treble.redhat.com> <20150221183005.GB8406@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: 1253 Lines: 33 On Sat, 21 Feb 2015, Ingo Molnar wrote: > > Plus a lot of processes would see EINTR, causing more havoc. > > Parking threads safely in user mode does not require the propagation of > syscall interruption to user-space. BTW how exactly do you envision this will work? Do I understand your proposal correctly that EINTR will be "handled" somewhere in the "live patching special signal handler" and then have the interrupted syscall restarted? Even without EINTR propagation to userspace, this would make a lot of new syscall restarts that were not there before, and I am still to be convinced that this is something we are not going to cause a lot of new user-visible breakage with. Yes, the breakage would be caused kernel bugs (I mostly envision drivers to be problematic in this area) that would be nice to have fixed, but the user experience that will come out of it will be just completely horrible. Or did I misunderstand what you are really proposing? 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/