public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Greg KH <greg@kroah.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	zaitcev@redhat.com
Subject: Re: Patch to add usbmon
Date: Wed, 2 Feb 2005 10:54:54 -0800	[thread overview]
Message-ID: <20050202105454.3f85dbdf@localhost.localdomain> (raw)
In-Reply-To: <1107362417.11944.7.camel@pegasus>

On Wed, 02 Feb 2005 17:40:17 +0100, Marcel Holtmann <marcel@holtmann.org> wrote:

> While I am really thinking about starting usbdump, I may ask why you
> have choosen to use debugfs as interface. This will not be available in
> normal distribution kernels and I think a general USB monitoring ability
> would be great. For example like we have it for Ethernet, Bluetooth and
> IrDA. So my idea is to create some /dev/usbmonX (for each bus one) where
> usbdump can read its information from. What do you think?

The debugfs will be available in distributions. And it's no different from
having SOCK_PACKET enabled before tcpdump can work. There's no practical
disadvantage, unless we consider a backport of usbmon into a legacy distribution
such as RHEL 4 or SuSE 9.1.

Since usbmon rides raw file_operations, it can use a chardev interface with
a minimal change. The advantage of debugfs is only not needing to allocate
a major and dealing with minor partitioning. I also thought it would help
to shut up the namespace pollution whiners (the debate of /dbg versus
/sys/kernel/debug was rather mild by comparison).

It should make little difference for the tool anyway, the base path ought to
be configurable. The biggest difference would be to scripts which launch the
tool: in one case they need to mount debugfs if not mounted (if initscripts
haven't), in other case they mknod if necessary (if hal hasn't done it).
It is too early to care about this anyway.

-- Pete

  reply	other threads:[~2005-02-02 19:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  5:29 Patch to add usbmon Pete Zaitcev
2005-02-01  7:10 ` Greg KH
2005-02-01  8:32   ` Pete Zaitcev
2005-02-01 11:13     ` Marcel Holtmann
2005-02-01 17:55       ` Pete Zaitcev
2005-02-01 21:37         ` Marcel Holtmann
2005-02-02  5:59           ` Pete Zaitcev
2005-02-02 16:40             ` Marcel Holtmann
2005-02-02 18:54               ` Pete Zaitcev [this message]
2005-02-05  0:19                 ` Marcel Holtmann
2005-02-02  6:25   ` Pete Zaitcev
2005-02-04 23:47     ` 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=20050202105454.3f85dbdf@localhost.localdomain \
    --to=zaitcev@redhat.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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