linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	linux-usb-devel@lists.sourcefoge.net.kroah.org,
	linux-kernel@vger.kernel.org, laforge@gnumonks.org
Subject: Re: My vision of usbmon
Date: Tue, 21 Dec 2004 21:04:24 -0800	[thread overview]
Message-ID: <20041222050424.GB31076@kroah.com> (raw)
In-Reply-To: <1103679534.5055.2.camel@npiggin-nld.site>

On Wed, Dec 22, 2004 at 12:38:54PM +1100, Nick Piggin wrote:
> On Tue, 2004-12-21 at 16:57 -0800, Greg KH wrote:
> > On Sun, Dec 19, 2004 at 11:04:54PM -0800, Pete Zaitcev wrote:
> > > Hi, Guys:
> > > 
> > > This is usbmon which I cooked up because I got tired from adding dbg()'s
> > > and polluting my dmesg. I use it to hunt bugs in USB storage devices so
> > > far, and it's useful, although limited at this stage.
> > > 
> > > I looked at the Harding's USBmon patch, and I think he got a few things right.
> > > The main of them is that I underestimated the benefits of placing the special
> > > files into the filesystem namespace. When we discussed it with Greg in the
> > > airport, we decided that having some sort of Netlink-style socket would be
> > > the best option. I decided to make a u-turn and attach those sockets into
> > > the namespace (currently under /dbg, but it can change). What this buys us is:
> > > 
> 
> Is there any reason why these debug filesystems are going under the
> root directory? Why not /sys/debug or /sys/kernel/debug or something?

See the previous thread as to where to mount debugfs.  In short, I don't
really care :)

thanks,

greg k-h

  reply	other threads:[~2004-12-22  5:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20  7:04 My vision of usbmon Pete Zaitcev
     [not found] ` <200412201255.59120.oliver@neukum.org>
2004-12-20 12:21   ` [linux-usb-devel] " Pete Zaitcev
2004-12-22  0:57 ` Greg KH
2004-12-22  1:29   ` Pete Zaitcev
2004-12-22  5:06     ` Greg KH
2004-12-22  5:10       ` Greg KH
2004-12-22  1:38   ` Nick Piggin
2004-12-22  5:04     ` Greg KH [this message]
2004-12-22  5:34       ` Jeff Garzik
2004-12-22  6:43         ` Greg KH
     [not found] ` <200412201525.52149.oliver@neukum.org>
2004-12-22  2:25   ` Pete Zaitcev
2004-12-22  5:03     ` Greg KH
2004-12-22 20:46     ` Oliver Neukum
2004-12-23 21:02 Chad Kitching
2005-01-11  1:36 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041222050424.GB31076@kroah.com \
    --to=greg@kroah.com \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourcefoge.net.kroah.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=zaitcev@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).