linux-kernel - Re: Commit *driver core: emit uevents when device is bound to a driver* causes regression

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180406132720.GA16189@kroah.com>
Date:   Fri, 6 Apr 2018 15:27:20 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Paul Menzel <pmenzel+linux-input@...gen.mpg.de>
Cc:     Michael Tokarev <mjt@....msk.ru>, linux-input@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Ben Caradoc-Davies <ben@...nsient.nz>,
        it+linux-input@...gen.mpg.de
Subject: Re: Commit *driver core: emit uevents when device is bound to a
 driver* causes regression

On Fri, Apr 06, 2018 at 03:24:39PM +0200, Paul Menzel wrote:
> Dear Greg,
> 
> 
> On 04/06/18 15:18, Greg Kroah-Hartman wrote:
> > On Fri, Apr 06, 2018 at 02:20:40PM +0200, Paul Menzel wrote:
> 
> > > 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?
> > 
> > I thought we fixed this with follow-on patches, are you sure you are
> > using the latest 4.14.y kernel that has been released?
> 
> Here we are using Linux 4.14.30. We can try newer versions next week.

Ah, no, 4.14.30 should be fine.

I saw the patch listed in the debian bug report, so this only happens
for the MTP type devices?  That was a really odd "filter" that it was
trying to use before.

So this is only for userspace programs, and one specifically?  And for
only one type of device?  What device, MTP devices?

thanks,

greg k-h