From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CF728C433FE for ; Mon, 4 Oct 2021 15:44:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B359D6113A for ; Mon, 4 Oct 2021 15:44:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235864AbhJDPq3 (ORCPT ); Mon, 4 Oct 2021 11:46:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39286 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235455AbhJDPq1 (ORCPT ); Mon, 4 Oct 2021 11:46:27 -0400 Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 77DEDC06174E for ; Mon, 4 Oct 2021 08:44:38 -0700 (PDT) Received: by mail-qk1-x72b.google.com with SMTP id d207so6296061qkg.0 for ; Mon, 04 Oct 2021 08:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=0/aP63vy196i8qH5aGLzYmPHF4Nnb+LayDyFtr1MXMg=; b=FrrVaLmatO49LvYV8N9t8dOdbGVBJR3uVBoq9V1WS6cSj2Cb1rm4irSPU637X3Eyv9 XYle6u16GK8tqSmcZsxSml+QoQhROr2ixOlYw/HLYJ0moUkyLT+ARSKEyFM4P2Vf2aVZ bHQ5rlQcKN7lXDC26PuHAyymZGCME2n3eKQruQF7BGnnssj52apDsqZ47vaw7CneEVj0 FbmRF1DEjIiJ6n+vrG4P3iETCVLbIN9IA29e3wqYeJm8Q7sCRb8NuFBkaHIhfa0kgUe7 OTTt++eukDUH5MZyWsRhjylFCBO9ap9F9k0d6VFXYGnSLUhrgW/TGUYiQYgBmpTnuwrV 3xsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=0/aP63vy196i8qH5aGLzYmPHF4Nnb+LayDyFtr1MXMg=; b=N+yoV/Cj/4qoUDAUAt5lop3loKWeYsxPe5LeljU4IF1EZHedorU55XsT6vDQc0qLgQ rW+MP1DhlZYU46xTRLawbrtoMF+rmSjnOgZuKaD6sidsLO7Gn97fnOVeR2PR7xbbKCkB hbplg0yh8CcUyqiLzLORRlEMFk6Ph0seWfp+rLZK6Jwlurxcq3h0kctET7wS3zTHKZqo g1sCTJoXLGG+n8+dlXv5VXGnUUZSNGFo1k6xe8P8+a6PYZrmx0Q4KCIqBocUnao02YDz v5TUkRpdwzgSVSrorBd/kmP0kQUmIFu6Po60gizkKA0+BwH/YaHuAd+Y56jeBY4pf1hD sXRA== X-Gm-Message-State: AOAM5313nROcuCJlwdw+8oRc6a2SxNdclyLmFHeZ5gW4JBAJUJPmMTbO TtxhCxc6Vd+P0gxjOr084A2nRw== X-Google-Smtp-Source: ABdhPJzmrnxoimB1jf2ei4cUIinalbPGsZ26WCIenMwLucficq046xW8YP3iE+lNnoSolu8XpL/UpQ== X-Received: by 2002:a37:670d:: with SMTP id b13mr10467091qkc.420.1633362277573; Mon, 04 Oct 2021 08:44:37 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-142-162-113-129.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.162.113.129]) by smtp.gmail.com with ESMTPSA id h66sm7850926qkc.5.2021.10.04.08.44.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Oct 2021 08:44:36 -0700 (PDT) Received: from jgg by mlx with local (Exim 4.94) (envelope-from ) id 1mXQ8q-00AW43-2f; Mon, 04 Oct 2021 12:44:36 -0300 Date: Mon, 4 Oct 2021 12:44:36 -0300 From: Jason Gunthorpe To: Mark Brown Cc: Lino Sanfilippo , f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com, bcm-kernel-feedback-list@broadcom.com, nsaenz@kernel.org, linux-spi@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, p.rosenberger@kunbus.com, linux-integrity@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH] spi: bcm2835: do not unregister controller in shutdown handler Message-ID: <20211004154436.GY3544071@ziepe.ca> References: <20210928195657.5573-1-LinoSanfilippo@gmx.de> <20211001175422.GA53652@sirena.org.uk> <2c4d7115-7a02-f79e-c91b-3c2dd54051b2@gmx.de> <20211004131756.GW3544071@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 04, 2021 at 03:12:20PM +0100, Mark Brown wrote: > On Mon, Oct 04, 2021 at 10:17:56AM -0300, Jason Gunthorpe wrote: > > > Shutdown is supposed to quiet the HW so it is not doing DMAs any > > more. This is basically an 'emergency' kind of path, the HW should be > > violently stopped if available - ie clearing the bus master bits on > > PCI, for instance. > > > When something like kexec happens we need the machine to be in a state > > where random DMA's are not corrupting memory. > > That's all well and good but there's no point in implementing something > half baked that's opening up a whole bunch of opportunities to crash the > system if more work comes in after it's half broken the device setup. Well, that is up to the driver implementing this. It looks like device shutdown is called before the userspace is all nuked so yes, concurrency with userspace is a possible concern here. > > Due to the emergency sort of nature it is not appropriate to do > > locking complicated sorts of things like struct device unregistrations > > here. > > That's just not what's actually implemented in a bunch of places, nor > something one would infer from the documentation ("Called at shut-down > to quiesce the device", no mention of emergency cases which I'd guess > would just be kdump) - Drivers mis understanding stuff is not new.. > that's a different thing and definitely abusing the API. I would guess > that a good proportion of people implementing it are more worried about > clean system shutdown than they are about kdump. The other important case is to get the device cleaned up enough to pass back to firmware for platforms that use a firmware shutdown/reboot path. Jason