Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp806356ybe; Thu, 5 Sep 2019 06:17:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqwMMQFeesScmndXcoGxV9TG/vnkTYRb+8KIRf/n4MDf+mGzDQSpGYhJA9qVSB84MlJ7tcXN X-Received: by 2002:a17:902:a5c5:: with SMTP id t5mr3205928plq.316.1567689464803; Thu, 05 Sep 2019 06:17:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567689464; cv=none; d=google.com; s=arc-20160816; b=X6nwwDnk/j+XLNPme6j/J/Z2RUGSBBes7CbsdF5ysYP9N6zONEAiNzDd51khJ0R8fN vgix2qAQIkAq5x6gFyhC4SfNkA2QhpDTEVLS9lBCZ/vg0bqo8jt/S5XDYChJ1bfVAbX9 RBhMkblF/keSsURzdq1hwy8XZXezRIFjRbFJGR8JvBw/uWuLj0r8McUTVuJ7KeO+zCBo 3uoEyYj6mJbbLpUcXUzNhGbSGhLizcvF2+ZjlrCg+0AVIO89sLU9rM+CrLgcd4dlljeI TNDdlp8hxGCCIFIS4B43bfL3cj73g3shi88scHASlD/gE9UmT4UrV7OMXAoe5Ox/Nj5S DvOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=Fu500Z6Csqx83M9yTT1Ivm+s2+LDEWv7iithCwHHUYc=; b=tIaP26mtmK0UZnvrmf9eApBh9YPyFmCr5qtXmDJjEQuRogmX/fROa4hJMdae30f1Hv VZWoqrQU0ULSoqt3nV13s6u+92/FP7u5MZ2K70KIUsPN2SlXPuOEfYD8MQz7NpZ61iZS rT0aVREEpHieFjulIlZPXycKoX2fJI1qhu+81L8Xb0aHy6NQAXWLzhYRtc+D5d+LK5w+ UW8aMDFFj3Tl4/4Q2EgAm2gJCZDOSBCFBbIh0i0F913GNJTlwVrfFDN4htsIYwD4NQLm xIBtehZOkKZEfNs99COWUhDOqfOEdVTdXocuuSVuwo7dxW+RKgIw8nANblzY67E9EG7w E+7w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d4si2027657pjj.28.2019.09.05.06.17.27; Thu, 05 Sep 2019 06:17:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732996AbfIELw6 (ORCPT + 99 others); Thu, 5 Sep 2019 07:52:58 -0400 Received: from mx2.suse.de ([195.135.220.15]:58488 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725921AbfIELw5 (ORCPT ); Thu, 5 Sep 2019 07:52:57 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 8A64BAEF8; Thu, 5 Sep 2019 11:52:56 +0000 (UTC) Date: Thu, 5 Sep 2019 13:52:42 +0200 (CEST) From: Miroslav Benes To: Petr Mladek cc: Joe Lawrence , jikos@kernel.org, Josh Poimboeuf , linux-kernel@vger.kernel.org, live-patching@vger.kernel.org Subject: Re: [RFC PATCH 2/2] livepatch: Clear relocation targets on a module removal In-Reply-To: <20190904084932.gndrtewubqiaxmzy@pathway.suse.cz> Message-ID: References: <20190728200427.dbrojgu7hafphia7@treble> <20190814151244.5xoaxib5iya2qjco@treble> <20190816094608.3p2z73oxcoqavnm4@pathway.suse.cz> <20190822223649.ptg6e7qyvosrljqx@treble> <20190823081306.kbkm7b4deqrare2v@pathway.suse.cz> <20190826145449.wyo7avwpqyriem46@treble> <5c649320-a9bf-ae7f-5102-483bc34d219f@redhat.com> <20190904084932.gndrtewubqiaxmzy@pathway.suse.cz> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [...] > I wonder what is necessary for a productive discussion on Plumbers: [...] > + It might be useful to prepare overview of the existing proposals > and agree on the positives and negatives. I am afraid that some > of them might depend on the customer base and > use cases. Sometimes we might not have enough information. > But it might be good to get on the same page where possible. > > Anyway, it might rule out some variants so that we could better > concentrate on the acceptable ones. Or come with yet another > proposal that would avoid the real blockers. My plan is to describe the problem first for the public in the room. Then describe the proposals and their advantages and disadvantages. This should start the discussion pretty well. I would be happy if we managed to settle at least on the requirements for a solution. It seems that our experience with users and their use cases differ a lot and I doubt we could come up with a good solution without stating what we want (and don't want) first. Silly hope is that there may be someone with a perfect solution in the room. After all, it is what conferences are for. > Would it be better to discuss this in a separate room with > a whiteboard or paperboard? Maybe. Miroslav