Received: by 10.192.165.148 with SMTP id m20csp3381104imm; Mon, 7 May 2018 11:14:40 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrdNiIgbuzMN51ohXJrVchR2U+XVSyPXr59SdmeDxnDK3zBrN2nPdivEyce9OaKZvmQB2br X-Received: by 2002:a9d:2b72:: with SMTP id f47-v6mr25859900otd.69.1525716880677; Mon, 07 May 2018 11:14:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525716880; cv=none; d=google.com; s=arc-20160816; b=JCb7B1FEiDHLmhAkpBochIJrvSxhVkW8+ke3azxNXz6vzbhzelJoturFW3NefqsGQW eFribCmgta4L2L8lyIl96V7gzP8oApF01ZqHOXcK8E7gz0JXX7Os9GBsdBD4kcRmVGWt zia2a7+r2Csir86LDXnvUa86+6jtOMXjIh4p5TlZV/RcBjfhXBox52uOhNoUQmxNMRgk 0QwJkAsOsKijehWGyBU7IvhIvytdkyJHW6sTslJ/QAZby5Wqb59OouZt6NNyI1DeF2MK 4yQ4b9FNJs+ViHJl2pqKzJE4laCHQTDahWdRnzuMYxWUmeUx52Uh9qvZfDnHgcF0UeP6 F8aA== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=aIwoDZvhBTebv6UCrnA5L8W68tJB62L8GqVhE3VX/To=; b=N1H2R1khDzvRJEIAdA+Xr5JVDWmpxkr/XA86n24tG8Ww2CJiulhbVE0iLgg7Nc1Yl4 /GtAiKos1EiUofMrAkvz+IwUguOv00CySRsU9XROeizqZtEopEdONHO8bI9t4whdBD4X Pdf7kszkfO9tvyw6R9WjoAy9KnbgexSiy+KJj2b85XEf70NYRI058qCAZcg9qU/9KsZ4 Uo35Pd3uU5fhYoAjYj+X3i5vbqwql8DyjDZpp5h4u451j7mmLjcTiZGwtIKfQWHf190D b8zMOC3DhQiiuNKHPfoqaK9G7M2SQKu7K7WokA+HNBNQnDnwf+SE0C6yFI1uL+DEtwPw U/sw== ARC-Authentication-Results: i=1; mx.google.com; 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 s139-v6si8013793oih.100.2018.05.07.11.14.25; Mon, 07 May 2018 11:14:40 -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; 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 S1752352AbeEGSNt (ORCPT + 99 others); Mon, 7 May 2018 14:13:49 -0400 Received: from kawka.in.waw.pl ([178.62.225.244]:41303 "EHLO kawka.in.waw.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751951AbeEGSNs (ORCPT ); Mon, 7 May 2018 14:13:48 -0400 X-Greylist: delayed 1663 seconds by postgrey-1.27 at vger.kernel.org; Mon, 07 May 2018 14:13:47 EDT Received: from zbyszek by kawka.in.waw.pl with local (Exim 4.80) (envelope-from ) id 1fFkC3-0005Lx-2y; Mon, 07 May 2018 17:44:59 +0000 Date: Mon, 7 May 2018 17:44:59 +0000 From: Zbigniew =?utf-8?Q?J=C4=99drzejewski-Szmek?= To: Ville Syrjala Cc: linux-bluetooth@vger.kernel.org, Kay Sievers , systemd-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [systemd-devel] [PATCH bluez] hid2hci: Fix udev rules for linux-4.14+ Message-ID: <20180507174459.GH8805@in.waw.pl> References: <20180507130638.3516-1-ville.syrjala@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180507130638.3516-1-ville.syrjala@linux.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 07, 2018 at 04:06:38PM +0300, Ville Syrjala wrote: > From: Ville Syrj?l? > > Since commit 1455cf8dbfd0 ("driver core: emit uevents when > device is bound to a driver") the kernel started emitting > "bound" and "unbound" uevents which confuse the hid2hci > udev rules. > > The symptoms on an affected machine (Dell E5400 in my case) > include bluetooth devices not appearing and udev hogging > the cpu as it's busy processing a constant stream of these > "bound"+"unbound" uevents. > > Change the udev rules only kick in for an "add" event. > This seems to cure my machine at least. > > Cc: Dmitry Torokhov > Cc: Greg Kroah-Hartman > Cc: Marcel Holtmann > Cc: Kay Sievers > Cc: systemd-devel@lists.freedesktop.org > Cc: linux-kernel@vger.kernel.org > Cc: linux-bluetooth@vger.kernel.org > Signed-off-by: Ville Syrj?l? > --- > tools/hid2hci.rules | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/hid2hci.rules b/tools/hid2hci.rules > index db6bb03d2ef3..daa381d77387 100644 > --- a/tools/hid2hci.rules > +++ b/tools/hid2hci.rules > @@ -1,6 +1,6 @@ > # do not edit this file, it will be overwritten on update > > -ACTION=="remove", GOTO="hid2hci_end" > +ACTION!="add", GOTO="hid2hci_end" > SUBSYSTEM!="usb*", GOTO="hid2hci_end" This will skip over lines 22-23. Is the rule there supposed to work for ACTION==add only (in which case your patch would be OK), or also for ACTION==change? Maybe it'd be safer to just add the GOTO for bind/unbind. Zbyszek