Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp407126pxf; Wed, 7 Apr 2021 02:27:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx34Kb3niILblYWJyHpB/sg5iXiEh3u+KUnx0+WyVOI4U8VGCKSbwbhEcylTP6AA15ZTo1d X-Received: by 2002:a05:6402:84e:: with SMTP id b14mr3192724edz.194.1617787645779; Wed, 07 Apr 2021 02:27:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617787645; cv=none; d=google.com; s=arc-20160816; b=quVrX60gYkDRWlBjXU1D0yR+QA+bmfoTIkhe5UDrQEsJrvA2wHBhfWWdfo+dzxl7EL pKUnEvlTDtP4R0jTJ4eXb7UmVPYLRDaeK43k5Su9OYKCPtkCgMam2dIoMJ3EyEoPnhOB YOxkWBGPOJs3zof9daxJ1NSHOOfNkBK51HelD+4RfI/pRe0TB0Tm+4HzU8NstwIHgu+Y a11KPwwWhLNrM2I9xAnXFai3uteSlujbFudDYcDrRuKgl8HnESz6yHB5ZcKax4bFPgYn bZP37B14RtLS+cBXVvz5g1ArR0lnGrS+NtEOpqPxtceH6Qgk05ecAfm0O5pTrj/mXUxo K8rA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=GECg07lP5wsIqbFA2Q0Bw1H5A4ajMexc9b0QUtiEUWY=; b=J/EzjsQesqNtuaoAZw4y1iAUn8/BZQhKHcs8Vwc6TyWPsxmKXYrSkI3MuXWKGrClZr tqcYRplXYeK77DqESAxb3r9RaK9oVnvx5xcLOipUZQwnpG65B4GJFL3v5PIlihcD+0AD 2GeKPN26NqUe+cOH9Y9ePFaMfRAdjxYMbfCDsLKaUUsPcjGNf2XzpCjJpYMx2z4tBBn5 u7K6P0adpVXXE9FjkQHkT2AhZkwvD0b2V0lFVIGwObEj/jnugy8xpxT4VaA0lArsVpLK C8eHYbVPe0tpFCz4sXaHb2Z98wwzxqbgmJ+8hzdjeFzpUz+EEUo7Uw5x/P0dpgO6KjO5 YtEA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=cI2GLgvo; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v27si4862099eja.407.2021.04.07.02.27.02; Wed, 07 Apr 2021 02:27:25 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=cI2GLgvo; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230125AbhDFPyn (ORCPT + 99 others); Tue, 6 Apr 2021 11:54:43 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:28625 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243616AbhDFPym (ORCPT ); Tue, 6 Apr 2021 11:54:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1617724474; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GECg07lP5wsIqbFA2Q0Bw1H5A4ajMexc9b0QUtiEUWY=; b=cI2GLgvon9l6hRkwem95ROnHMUL7bW2cNgEzkDXSVnzsQ17pAnpgejx0EtKygdbrB0gsT8 lbMNGLvo/gqXqBzc2+tAc84LgDXvyNcI6K9y8W2JtZXXKclVTCxNrwyncZTL95u3LgqtJT awSHfEVxZYEI4JR9nLgU1R3jz0DqW9o= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-215-CUodGpTdMkqgH90ht6jzIw-1; Tue, 06 Apr 2021 11:54:30 -0400 X-MC-Unique: CUodGpTdMkqgH90ht6jzIw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 94AA2800D53; Tue, 6 Apr 2021 15:54:27 +0000 (UTC) Received: from treble (ovpn-116-68.rdu2.redhat.com [10.10.116.68]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6F97310016FC; Tue, 6 Apr 2021 15:54:25 +0000 (UTC) Date: Tue, 6 Apr 2021 10:54:23 -0500 From: Josh Poimboeuf To: Miroslav Benes Cc: Greg KH , Luis Chamberlain , 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, Jessica Yu , Peter Zijlstra Subject: Re: [PATCH 1/2] zram: fix crashes due to use of cpu hotplug multistate Message-ID: <20210406155423.t7dagp24bupudv3p@treble> References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 06, 2021 at 02:00:19PM +0200, Miroslav Benes wrote: > 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. Same for Red Hat. Unloading livepatch modules seems to work fine, but isn't officially supported. That said, if rmmod is just considered a development aid, and we're going to be ignoring bugs, we should make it official with a new TAINT_RMMOD. -- Josh