linux-kernel - Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another

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]

Date:	Thu, 7 Apr 2016 17:46:40 +0300
From:	Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>,
	Michal Nazarewicz <mina86@...a86.com>
Cc:	Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org,
	Felipe Balbi <felipe.balbi@...ux.intel.com>,
	Bin Liu <b-liu@...com>, pali.rohar@...il.com
Subject: Re: [PATCH] usb: f_mass_storage: test whether thread is running
 before starting another


Hi,

On  7.04.2016 17:25, Alan Stern wrote:
> On Thu, 7 Apr 2016, Michal Nazarewicz wrote:
>
>> Sounds good to me.  I’d love someone to test this patch (I sadly have no
>> way of doing that at the moment) and with that I can resend it with
>> updated message.
>
> Ivaylo should be able to try it.
>

I applied the patch agains 4.6-rc1 and while it seems there is no more 
oops, trying to "cd /sys/bus/platform/drivers/musb-hdrc && echo 
musb-hdrc.0.auto > unbind" still results in console hang. Will try to 
find time later today and put printks all over the place to see what's 
going on.

Ivo