From: David <david@unsolicited.net>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: John Stoffel <john@stoffel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas@winischhofer.net
Subject: Re: Patch to fix usbmon crash on Opteron
Date: Wed, 03 Jun 2009 19:22:01 +0100 [thread overview]
Message-ID: <4A26BF49.6040907@unsolicited.net> (raw)
In-Reply-To: <20090602210932.b74fff08.zaitcev@redhat.com>
Pete Zaitcev wrote:
> Here's my proposal: forget the clever-by-half tricks and simply use
> transfer_buffer. This should not only fix Opteron, but also future IOMMUs
> that Intel and AMD promise. It may also make usbmon useable on PPC at last.
>
> I think downsides are negligible. The ones I see are:
> - A driver may pass an address of one buffer down as transfer_buffer,
> and entirely different entity mapped for DMA, resulting in misleading
> output of usbmon.
> - Out of tree drivers may crash usbmon if they store garbage in
> transfer_buffer. I went over the tree with a comb and fixed obvious
> bugs, and clarified the documentation in comments.
> - Drivers that use get_user_pages will not be possible to monitor
> - Similar deal is with usb_storage transferring from highmem, but
> it works fine on 64-bit systems, so I think it's not a concern.
>
> I'm adding a sign-off line in case, but in general this is a patch
> for testing. In particular, sisusb is a concern.
>
> David & John, I am quite certain that your Opterons will not crash now,
> but please give it a try, and also you can use this code to produce usbmon
> traces you needed for debugging of other things.
>
> Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
>
>
Works fine on my system!
Cheers
David
next prev parent reply other threads:[~2009-06-03 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 3:09 Patch to fix usbmon crash on Opteron Pete Zaitcev
2009-06-03 14:24 ` John Stoffel
2009-06-03 18:22 ` David [this message]
2009-09-02 19:59 ` Simon Arlott
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=4A26BF49.6040907@unsolicited.net \
--to=david@unsolicited.net \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=thomas@winischhofer.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.