From: Paul Menzel <pmenzel+linux-input@molgen.mpg.de>
To: Michael Tokarev <mjt@tls.msk.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ben Caradoc-Davies <ben@transient.nz>
Subject: Commit *driver core: emit uevents when device is bound to a driver* causes regression
Date: Fri, 6 Apr 2018 14:20:40 +0200 [thread overview]
Message-ID: <8d22cfe6-90b6-eb86-d82e-0e037bfbed4e@molgen.mpg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Dear Linux folks,
Commit 1455cf8 (driver core: emit uevents when device is bound to a
driver) [1], introduced in Linux 4.14-rc1, causes a regression in user
space.
After disconnecting USB devices, they are still shown as plugged in [2][3].
> I seem to be having a similar issue, but with an iPhone X using USB
> to provide internet access. Even after the phone is disconnected, it
> still shows up as "loaded active plugged". The only way to fix this
> is to reboot or use a different USB port.
`git bisect` shows that commit 1455cf8 (driver core: emit uevents when
device is bound to a driver) is at fault [4].
As user space should not break with newer Linux kernels, do you know
what to do about that or can you think of a fix?
Kind regards,
Paul
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
[2] https://github.com/systemd/systemd/issues/7587
[3] https://bugs.debian.org/883425
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883425#68
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next reply other threads:[~2018-04-06 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 12:20 Paul Menzel [this message]
2018-04-06 12:47 ` Ben Caradoc-Davies
2018-04-06 13:18 ` Greg Kroah-Hartman
2018-04-06 13:24 ` Paul Menzel
2018-04-06 13:27 ` Greg Kroah-Hartman
2018-04-06 18:26 ` Dmitry Torokhov
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=8d22cfe6-90b6-eb86-d82e-0e037bfbed4e@molgen.mpg.de \
--to=pmenzel+linux-input@molgen.mpg.de \
--cc=ben@transient.nz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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
all inboxes | Powered by JetHome®