Hi,
[sorry if this is not the right point for reporting bugs, I took the email
addresses from MAINTAINERS but please point me to the correct place if needed]
I have an external USB drive (Samsung M3), which apparently uses the UAS code.
Starting with 4.4 (from Debian sid, I could retry with vanil
On mar., 2016-03-01 at 11:49 +0100, Hans de Goede wrote:
> Can you try building a kernel with the following line in
> drivers/usb/storage/uas.c :
>
> .can_queue = 65536, /* Is there a limit on the _host_ ? */
>
> (around line 815) Replaced with
>
> .can_queue = MAX_CMNDS,
>
On mar., 2016-03-01 at 11:49 +0100, Hans de Goede wrote:
> Hi,
>
> On 01-03-16 10:42, Yves-Alexis Perez wrote:
> >
> > Hi,
> >
> > [sorry if this is not the right point for reporting bugs, I took the email
> > addresses from MAINTAINERS but please poin
On ven., 2016-03-04 at 08:18 +0100, Hans de Goede wrote:
> Thanks for testing, there shouldn't be any side-effects, I'll turn this into
> a proper patch, add a:
>
> Reported-and-tested-by: Yves-Alexis Perez
>
> line to the comit msg and submit this upstream.
>
On ven., 2014-08-08 at 14:36 -0700, Greg KH wrote:
> On Fri, Aug 08, 2014 at 11:27:06PM +0200, Yves-Alexis Perez wrote:
> > On ven., 2014-08-08 at 14:20 -0700, Greg KH wrote:
> > > > Actually, since it's a module parameter, it doesn't seem possible to
> > >
On ven., 2014-08-08 at 18:17 -0400, Alan Stern wrote:
> The authorized_default module parameter affects USB buses when they
> are
> discovered and registered; after that it has no effect. Therefore to
> accomplish what you want, you need to put
> "usbcore.authorized_default=0" in the kernel's boot
On ven., 2014-08-08 at 18:26 -0400, Alan Stern wrote:
> I'm not sure what you mean. You can toggle these values at any time,
> but toggling them may not accomplish anything useful. What do you
> want
> to accomplish?
The point would be to prevent new usb device to be plugged while a
system is
On ven., 2014-08-08 at 18:50 -0400, Alan Stern wrote:
> On Sat, 9 Aug 2014, Yves-Alexis Perez wrote:
>
> > On ven., 2014-08-08 at 18:26 -0400, Alan Stern wrote:
> > > I'm not sure what you mean. You can toggle these values at any time,
> > > but toggling them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2018-11-23 at 13:51 +0100, Bernd Eckstein wrote:
> This causes the following problems:
> - double free of the skb or potential memory leak
> - in dmesg: 'recvmsg bug' and 'recvmsg bug 2' and eventually
> general protection fault
For what i
