linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org,
	Kay Sievers <kay.sievers@vrfy.org>,
	systemd-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [systemd-devel] [PATCH bluez] hid2hci: Fix udev rules for linux-4.14+
Date: Mon, 7 May 2018 17:44:59 +0000	[thread overview]
Message-ID: <20180507174459.GH8805@in.waw.pl> (raw)
In-Reply-To: <20180507130638.3516-1-ville.syrjala@linux.intel.com>

On Mon, May 07, 2018 at 04:06:38PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> 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 <dmitry.torokhov@gmail.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Marcel Holtmann <marcel@holtmann.org>
> Cc: Kay Sievers <kay.sievers@vrfy.org>
> Cc: systemd-devel@lists.freedesktop.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-bluetooth@vger.kernel.org
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  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

  reply	other threads:[~2018-05-07 18:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 13:06 [PATCH bluez] hid2hci: Fix udev rules for linux-4.14+ Ville Syrjala
2018-05-07 17:44 ` Zbigniew Jędrzejewski-Szmek [this message]
2018-06-20 16:46   ` [systemd-devel] " Ville Syrjälä
2018-06-20 16:42 ` [PATCH v2] " Ville Syrjala
2018-11-05 17:54   ` Ville Syrjälä
2018-12-04 20:41   ` [PATCH v2 BlueZ] " Ville Syrjala
2018-12-05  7:06     ` Greg Kroah-Hartman
2018-12-05 15:40       ` Ville Syrjälä
2018-12-05 19:09         ` Dag B
2018-12-05 19:21           ` Greg Kroah-Hartman
2018-12-05 19:20         ` Greg Kroah-Hartman
2018-12-05 19:40           ` Ville Syrjälä
2018-12-05 19:49             ` Greg Kroah-Hartman
2019-04-23 15:41               ` Ville Syrjälä

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180507174459.GH8805@in.waw.pl \
    --to=zbyszek@in.waw.pl \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).