Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp30762pxf; Tue, 6 Apr 2021 14:05:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwy7onr6PrypWxx6Zq/C6L/k+Bh3N+1IfcW7SzEUM5WZxDMKs76oSbULPj0CPXomCLR2tr8 X-Received: by 2002:aa7:d88b:: with SMTP id u11mr335553edq.254.1617743111312; Tue, 06 Apr 2021 14:05:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617743111; cv=none; d=google.com; s=arc-20160816; b=nWCDfnY6LZI6dilz5Frq/SRjHFLZfAifcZROqzoSuMTqV8JAjdU/1bxsnG0tbaU0kc /rdmFtkFLyZWusR28dJeZSQskil2syDKsbmGQXZC6XP9HcCvTMM/bk2b8EBGjtXfMyIE 1zsIY6Q1CjnNgCTuOZ0Tgs6FWIO/NElWQntihOi1r+qhbHyVakuuZzilULMKTIwUWpAG x6ZcelviZBr08EN/NWDkxDj6/W5yYQSQiSCPVq2o0t8dp7vc/jDEEGHMVLPihG186Bmt bwXwwUTRPWZMx5DXckGuFFdN8xCMCuAAjVJTwtUMzDASvetG4PlazhcBjFF+jKR1hynS 0b3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=NaaQJXgYcP08GrnwoI2VEhNLVgXjp1HZ+cyC8eu4K6M=; b=eec/R9k1mbGuZvvJKJTl1mTFI+/y6JsOEXUHdYu/pTyWBsEBWHpFQjj5rbjphvOD4e iNn474da3xUddnDjIzTubAPyxsYiohYgjejM11tmpGGo3yoU4fbk3kIvkgtRWePIKlyV ApaTuWhAJPLradMjuONBVG1oIC2P4NPLtDxiMoIwVu/3V19Pab4mWqC6xtDGWC8nnzgl RSiAyUf2m0LibGa+aeDl35q8P3xu0PNFW2JHusPb8gF/oTjTfqE58sEQicY7N25lSQLJ PheH9//I6YAjeQTx+X4k8q86X2FBXuZlwXsfs6AKOa4xVuWjBG67F1YO8MMh8mbnbHSj 2bgA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s9si17228437edc.296.2021.04.06.14.04.48; Tue, 06 Apr 2021 14:05:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343652AbhDFMAa (ORCPT + 99 others); Tue, 6 Apr 2021 08:00:30 -0400 Received: from mx2.suse.de ([195.135.220.15]:48934 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343634AbhDFMA3 (ORCPT ); Tue, 6 Apr 2021 08:00:29 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id BD70EB15D; Tue, 6 Apr 2021 12:00:19 +0000 (UTC) Date: Tue, 6 Apr 2021 14:00:19 +0200 (CEST) From: Miroslav Benes To: Greg KH , Luis Chamberlain cc: mbenes@suse.com, Minchan Kim , keescook@chromium.org, dhowells@redhat.com, hch@infradead.org, ngupta@vflare.org, sergey.senozhatsky.work@gmail.com, axboe@kernel.dk, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, live-patching@vger.kernel.org Subject: Re: [PATCH 1/2] zram: fix crashes due to use of cpu hotplug multistate In-Reply-To: <20210406003152.GZ4332@42.do-not-panic.com> Message-ID: References: <20210312183238.GW4332@42.do-not-panic.com> <20210319190924.GK4332@42.do-not-panic.com> <20210322204156.GM4332@42.do-not-panic.com> <20210401235925.GR4332@42.do-not-panic.com> <20210402183016.GU4332@42.do-not-panic.com> <20210406003152.GZ4332@42.do-not-panic.com> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, > > Driver developers will simply have to open code these protections. In > > light of what I see on LTP / fuzzing, I suspect the use case will grow > > and we'll have to revisit this in the future. But for now, sure, we can > > just open code the required protections everywhere to not crash on module > > removal. > > LTP and fuzzing too do not remove modules. So I do not understand the > root problem here, that's just something that does not happen on a real > system. If I am not mistaken, the issue that Luis tries to solve here was indeed found by running LTP. > On Sat, Apr 03, 2021 at 08:13:23AM +0200, Greg KH wrote: > > On Fri, Apr 02, 2021 at 06:30:16PM +0000, Luis Chamberlain wrote: > > > On Fri, Apr 02, 2021 at 09:54:12AM +0200, Greg KH wrote: > > > > No, please no. Module removal is a "best effort", > > > > > > Not for live patching. I am not sure if I am missing any other valid > > > use case? > > > > live patching removes modules? We have so many code paths that are > > "best effort" when it comes to module unloading, trying to resolve this > > one is a valiant try, but not realistic. > > Miroslav, your input / help here would be valuable. I did the > generalization work because you said it would be worthy for you too... Yes, we have the option to revert and remove the existing live patch from the system. I am not sure how (if) it is used in practice. At least at SUSE we do not support the option. But we are only one of the many downstream users. So yes, there is the option. Miroslav