Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp1706180ybg; Wed, 29 Jul 2020 23:55:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzcm8duXj4fh0FmEuIHKMmRpauCZ+dP55CZpQXZsQ4kauDuVlFjHSxITeoZL8FTathZnXsO X-Received: by 2002:a17:906:1104:: with SMTP id h4mr1227514eja.456.1596092151716; Wed, 29 Jul 2020 23:55:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596092151; cv=none; d=google.com; s=arc-20160816; b=Mdyy1D5hf5xuGpZDM/KzQQ2SPB1ohTXqnmSWG8UbDPzzNuImv5uv9dl1usfSvsZY/v JeeC4jGap0bcDLsGqe3sh6RZHH0EMX95JQZ0PKDcrma7weNgN1s1FYIXQ3a7CTZ34uem g0Y9s+muti6yg4uNc9Xvrcw7CKYNUgmm+zE2//eX/XQj+fys18DeIhtesB/mHcbfmvMy aTW/Nb/Pb9yCasxG+NBcDXOd31F/8emmPQQ43q+pSd41iLv+Bo8A8QaxgQymkHttL/za bKv3r39l0EBkKqjemhrlnVqBiGOSngCqQzlMd2CEiNG1MfI01wXPnCQxHr/HvD+uXzRv 0aKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=wTxaNm/2ZhFx003Sq2GpUbmJ2XMFNdUbTUKbkWIRVR8=; b=BBHINoKXqQZHHHYENdlzpZS0n3OJP59tcN4cexj/w+Cd1Yo0FkbSZYR8YzNns/RyVc ArnUk8P5N1hRMSsCz7ArAaOxfkcCz9kv9c6aROeL+KbHoigo/c9N9YNGQbGOVoRE37xv fsRCI6b3uXQNgN7HNMd/E36nQ0ky3dZElFbnjAeMbLU/P69mfrbYD86lauyVIN4Hmp4C kzbISNLmlqewiHPMAMaRm7nxe1jKX44mJy85tJRvIl2pIctn6IQGzZV6nKtITDybzbi+ dnXO44E19Qbj5g5kMA4LTlAc/iSTSHSov2OK/wSaqsEQoC0HhGxUylm5h3IYYLJxd+11 gPmQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YNgL4iJr; 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 u12si1977030eja.519.2020.07.29.23.55.29; Wed, 29 Jul 2020 23:55:51 -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=@kernel.org header.s=default header.b=YNgL4iJr; 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 S1728797AbgG3GyR (ORCPT + 99 others); Thu, 30 Jul 2020 02:54:17 -0400 Received: from mail.kernel.org ([198.145.29.99]:45764 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726133AbgG3GyQ (ORCPT ); Thu, 30 Jul 2020 02:54:16 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 02E1020656; Thu, 30 Jul 2020 06:54:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596092056; bh=d2mGG9EZHjTB3Y/Qq+mlIWfyToju/xTDhzWBPh0dPi0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YNgL4iJrNhPxP84amUMEWzJvpIqTrTJPNZpqibJeVn+6nfEkqmMrF0aqAxtWBsbX5 GmiV+b5XlJJ3+nuCOcfE6kKV5h85reJQTJg8rOboAHqhjoMgbkT6AKMNN4aPqVokp7 ShP3e6+Aw7/+hl42kh12ZFMcxlMED0T1gX9AhXgk= Date: Thu, 30 Jul 2020 08:54:06 +0200 From: Greg Kroah-Hartman To: Lukas Wunner Cc: "Rafael J. Wysocki" , Dan Williams , Geert Uytterhoeven , Pantelis Antoniou , Alexander Duyck , Mark Brown , linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org Subject: Re: [PATCH 0/3] Fix races on device removal Message-ID: <20200730065406.GB3950394@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 08, 2020 at 03:27:00PM +0200, Lukas Wunner wrote: > Prevent dynamic SPI device addition below a controller which is > being removed. To do so, set the controller's "dead" flag using > kill_device() (patch [3/3]). Why is the SPI bus allowing this to happen? Don't you have a per-bus lock that can serialize all of this? thanks, greg k-h