Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1931976ybe; Tue, 3 Sep 2019 05:47:47 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJGn8Ry6xZUIy3n1l7RNBapBiAUeq2iSJNs37aa7UMD6vXsA1lVBwRAuniep4hEUoCLr1E X-Received: by 2002:a63:d34c:: with SMTP id u12mr30503767pgi.114.1567514867096; Tue, 03 Sep 2019 05:47:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567514867; cv=none; d=google.com; s=arc-20160816; b=aRD4Y5aqmATsp2qtsGxUKcG9OPWwaCRII9cXhBQJoUs+Ivw/n/Ve1EFDgPLlKvvkon oWD3I8E01JnPpfIr7MMET8vFv0BPjQLVD2dag/Yp1dmltKzS+oTuthqn/nqD5MbFj1N0 7fPiUmK3u4d682HmSQxotnvnPtQcJz4NzDUsam/mPnP0/8ZQ1NVpKQRhqXbTHU7+M91c 8TuKw+W6RogChoV9yyd842LuRyGeMSoQiU6C9JxD7Pdb313ch+47b0lupwKRzsvQeBZJ 5V+ceXq1kFccxhm7MA87WGzTtGwSeeCmS+wK1igbQ6rR1bNTXiAr2DOhdwNO6QNBdw66 FCEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=MIZWO/r5WYB1ZmJJ7B8lddyJnVFyg+qUjv42zSxUqt0=; b=Id7/cr8m2tDzOiYM5FQ2Vc8Hzd41642nqTGjjOzjUuQFxxDvZtx0QwyGOw96Uc0a09 t7uKy5WkbHkbnURHjeREG7lhbj+U58xtMclrKzL/BWQqmO3NCqLaa4p0Ujt/9Jbk4LyF A8daKf4wowJ4P6lNsnSmdcX7J6ae/lSDD9pr0DzeJSq/keEgDuueiNKOwU63Zf9NyDIT 9yceihszW0fVyiaE0OKI2uSc8P+GW06pD2YROF4l4FMyuqv7cGW6JEEsX2waDhNy0LSE FvvnUNf9NOriwWx2FA7gxOWKAh7kGQIjZ5gVi5Nmnd0FtRc4NzpVIHhiOqLz//Zccfl2 q80w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=YpxITNYJ; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=PwfKBbhs; 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 q128si17670037pfb.192.2019.09.03.05.47.31; Tue, 03 Sep 2019 05:47:47 -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; dkim=pass header.i=@kroah.com header.s=fm1 header.b=YpxITNYJ; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=PwfKBbhs; 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 S1729154AbfICMpb (ORCPT + 99 others); Tue, 3 Sep 2019 08:45:31 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:55323 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725782AbfICMpa (ORCPT ); Tue, 3 Sep 2019 08:45:30 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BE72421F2E; Tue, 3 Sep 2019 08:45:29 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 03 Sep 2019 08:45:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=MIZWO/r5WYB1ZmJJ7B8lddyJnVF yg+qUjv42zSxUqt0=; b=YpxITNYJslSW1rZgpIoPl5+IM9y17nEwlw4O7z2QmG7 SFyWS6hscPNDH/RBVBpP6XAvURfgbip1bM/4DmR3slsgnPCeq/CSBndgNRbq+qcB MFVztMkcLRCkvswpbB6WT1MNMnOSGRsV7WweL+jBHtiQtavnxOendn+JBWZ6h+PL UuUecnKYOBA84l7Dmo2Wub1ssIulrupTd+xz7tkYySrVEhIPcaHe7lDkTiUglaO2 mUJJyPlNU7JcetuWjtyQzQdmXtJ34qQUcf1LRKORpeou2kxu38zKS11NySdEDNaY vD9Mc/GlW+PPORuRS1pnlJ2QC2IlXuLOudnUTamQpsA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=MIZWO/ r5WYB1ZmJJ7B8lddyJnVFyg+qUjv42zSxUqt0=; b=PwfKBbhs0K48qaOLrvdzE5 pnSCoTF02Nc0tuXuMuJ6ECD9L09iHhA4JPiQPVLi8jqgbvgrmKk/vEf1AdrEzXNu ot8Ni4Sxr4OpitfZYZmyRdNvSevN9oMTuCmbJj5RF60ZpAXReDS1yyrzmE+zL0kN pwRo1I08so8k7txh1/6CtR6Xs+PEElDKwtKyiQjKIl0zQLivScXT+wfVeNbJ2C1+ Kije2LAwXPQAje3EbbCd/5DieXpKfIXUQSHfVriQ5zqFy1tpEBlu0xI07eVCGvBX Cm86foaabB9v4kxUVqMkY/xRlltWPnU9AtAuyjIcYG2q9SW/zHDH6MnzN3Me7krA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejfedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecukfhppeekfedrkeeirdekledrud dtjeenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhmnecu vehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id F2908D60068; Tue, 3 Sep 2019 08:45:28 -0400 (EDT) Date: Tue, 3 Sep 2019 14:45:27 +0200 From: Greg KH To: Oliver Neukum Cc: Julius Werner , USB Storage list , Dan Williams , Alan Stern , Kernel development list , USB list Subject: Re: [PATCH] usb: storage: Add ums-cros-aoa driver Message-ID: <20190903124527.GB493@kroah.com> References: <20190902164724.GA22619@kroah.com> <1567500374.2878.2.camel@suse.com> <20190903091953.GA12325@kroah.com> <1567505043.2878.4.camel@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1567505043.2878.4.camel@suse.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 03, 2019 at 12:04:03PM +0200, Oliver Neukum wrote: > Am Dienstag, den 03.09.2019, 11:19 +0200 schrieb Greg KH: > > On Tue, Sep 03, 2019 at 10:46:14AM +0200, Oliver Neukum wrote: > > > Am Montag, den 02.09.2019, 18:47 +0200 schrieb Greg KH: > > > > > > > > This should work just fine today. Add a new device id to the "new_id" > > > > file and then tell the driver to bind. That's pretty much the same as a > > > > "force_bind", right? > > > > > > That looks like a race condition by design to me. > > > > How? > > You have one of these files and potentially multiple devices > to be bound. You need a locking scheme. As soon as the acts > of specifying and binding are distinct. What needs to be locked here? totally confused, greg k-h