From: "John Stoffel" <john@stoffel.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: "John Stoffel" <john@stoffel.org>,
Jarek Poplawski <jarkao2@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: usb_mon oops Re: tcpdump crashes 2.6.29.1 (and 2.6.29-rc5)
Date: Wed, 8 Apr 2009 09:20:54 -0400 [thread overview]
Message-ID: <18908.42166.404232.721757@stoffel.org> (raw)
In-Reply-To: <20090407130403.e0061a8d.zaitcev@redhat.com>
Pete> On Tue, 7 Apr 2009 11:25:40 -0400, "John Stoffel" <john@stoffel.org> wrote:
>> But I'm surprised that USB_MON would be the cause when it's a
>> networking tool which is starting up? *shrug*
Pete> The libpcap supports usbmon. Perhaps it scans something.
Pete> The big problem with usbmon is, it has to trust what drivers
Pete> stuff into URBs. Bet it's your uvcvideo. A rough driver, that.
Well I think that usbmon is probably at fault here for trusting
drivers too much and not doing any sanity checking. But I can try
removing the uvcvideo driver and seeing if I can get the system to
crash then.
I was busy last night and didn't have a chance to even touch the
system. Hopefully more time tonight, but I'm not sure.
Thanks for the hints, I'll give them a whirl.
John
next prev parent reply other threads:[~2009-04-08 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 3:03 tcpdump crashes 2.6.29.1 (and 2.6.29-rc5) John Stoffel
2009-04-07 12:00 ` usb_mon oops " Jarek Poplawski
2009-04-07 15:25 ` John Stoffel
2009-04-07 18:52 ` John Stoffel
2009-04-07 19:04 ` Pete Zaitcev
2009-04-08 13:20 ` John Stoffel [this message]
2009-04-09 5:23 ` Pete Zaitcev
2009-04-09 13:59 ` John Stoffel
2009-04-13 23:41 ` Pete Zaitcev
2009-04-14 13:38 ` John Stoffel
2009-04-17 3:00 ` John Stoffel
2009-04-17 18:09 ` Pete Zaitcev
2009-04-10 3:01 ` John Stoffel
2009-04-10 6:24 ` Pete Zaitcev
2009-04-10 15:18 ` John Stoffel
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=18908.42166.404232.721757@stoffel.org \
--to=john@stoffel.org \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).