linux-kernel - Re: [00/03] [RFC] USB debugging rework

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: <20080810033548.GA30733@kroah.com>
Date:	Sat, 9 Aug 2008 20:35:48 -0700
From:	Greg KH <greg@...ah.com>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [00/03] [RFC] USB debugging rework

On Sat, Aug 09, 2008 at 04:04:22PM -0600, Pete Zaitcev wrote:
> On Fri, 8 Aug 2008 18:38:21 -0700, Greg KH <greg@...ah.com> wrote:
> 
> > I've been annoyed for a long time that we make users go off and rebuild
> > their kernels just to enable usb debug messages.  So finally, here's the
> > start of fixing that issue.
> 
> In many cases usbmon does the job, and it's intended to be "always-on",
> as to allow building it even on embedded kernels. Sure, it will not print
> nice values of quirks and such, but that's a trade-off. I sort of hoped
> that the switcheable explicit messages would generally die off. Look
> at ub, it only has messages which indicate error conditions.

And that's great, but for some problems we seem to keep needing to
enable debugging for either the core or the host controllers.  This
change should help with that.

thanks,

greg k-h
--
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/