linux-kernel - Re: [Patch] Increase USBFS Bulk Transfer size

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: <20111013200526.74fcc87b@lxorguk.ukuu.org.uk>
Date:	Thu, 13 Oct 2011 20:05:26 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Markus Rechberger <mrechberger@...il.com>,
	Greg KH <gregkh@...e.de>, USB list <linux-usb@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Patch] Increase USBFS Bulk Transfer size

> For my part, I don't much mind raising the limit from 16 KB to 32 KB.  
> 48 KB may be unnecessary, especially since one of the devices doesn't 
> even work when the transfer buffer is that large.
> 
> However it's just a work-around, not a real solution to the underlying
> problem (whatever that problem turns out to be).  Part of the reason
> for keeping the limit low is that it shouldn't matter, since people
> ought to be able to use a bunch of small transfers rather than one
> large transfer.  Apparently that justification doesn't work with these
> webcams, although there's no known reason why it shouldn't.
> 
> But I'm not the person in charge of these decisions...

Well if the underlying solution is crap hardware with no work around its
a bit hard to avoid. A more conservative approach would be to put the
'constant' in sysfs where it belongs so it can be adjusted and special
cased.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/