On Qua, 2014-08-06 at 08:25 -0700, Greg KH wrote:
> On Wed, Aug 06, 2014 at 04:12:20PM +0100, Sérgio Basto wrote:
> > On Qua, 2014-08-06 at 07:43 -0700, Greg KH wrote:
> > > On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> > > > Hi,
> > > >
> > > > we need a kernel with patch on [
On Wed, Aug 06, 2014 at 04:12:20PM +0100, Sérgio Basto wrote:
> On Qua, 2014-08-06 at 07:43 -0700, Greg KH wrote:
> > On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> > > Hi,
> > >
> > > we need a kernel with patch on [1] to usb works on guests machine of
> > > VirtualBox without
On Qua, 2014-08-06 at 07:43 -0700, Greg KH wrote:
> On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> > Hi,
> >
> > we need a kernel with patch on [1] to usb works on guests machine of
> > VirtualBox without spam dmesg.
>
> Then build such a kernel, what is preventing that?
I did
On Wed, Aug 06, 2014 at 02:42:31PM +0100, Sérgio Basto wrote:
> Hi,
>
> we need a kernel with patch on [1] to usb works on guests machine of
> VirtualBox without spam dmesg.
Then build such a kernel, what is preventing that?
> I tested patch [1] devio: fix issue with log flooding of message and
Hi,
we need a kernel with patch on [1] to usb works on guests machine of
VirtualBox without spam dmesg.
I tested patch [1] devio: fix issue with log flooding of message and it
works, I wonder if this patch will be applied to kernel or not ? and if
can go to stables or not ?
The problem of this
On Fri, 2014-08-01 at 10:45 -0400, Alan Stern wrote:
> It was a real question. You're right that this is a pretty unimportant
> kind of error. The question is whether anybody cares enough to want to
> fix it.
I guess the answer is no. The people who might care know now.
Regards
On Fri, 1 Aug 2014, Oliver Neukum wrote:
> On Fri, 2014-08-01 at 10:24 -0400, Alan Stern wrote:
> > On Fri, 1 Aug 2014, Oliver Neukum wrote:
> >
> > > usbfs allows user space to pass down an URB which sets URB_SHORT_NOT_OK
> > > for output URBs. That causes usbcore to log messages without limit
>
On Fri, 2014-08-01 at 10:24 -0400, Alan Stern wrote:
> On Fri, 1 Aug 2014, Oliver Neukum wrote:
>
> > usbfs allows user space to pass down an URB which sets URB_SHORT_NOT_OK
> > for output URBs. That causes usbcore to log messages without limit
> > for a nonsensical disallowed combination. The fix
On Fri, 1 Aug 2014, Oliver Neukum wrote:
> usbfs allows user space to pass down an URB which sets URB_SHORT_NOT_OK
> for output URBs. That causes usbcore to log messages without limit
> for a nonsensical disallowed combination. The fix is to silently drop
> the attribute in usbfs.
> The problem is
