From: Thomas Huth <thuth@redhat.com>
To: benlunt@fysnet.net, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] hw/us/bus.c PCAP adding 0xA in Windows version
Date: Fri, 1 Mar 2024 09:18:54 +0100 [thread overview]
Message-ID: <56e58fe0-476c-4daf-b61c-3fc24d7623a5@redhat.com> (raw)
In-Reply-To: <000101da6823$ce1bbf80$6a533e80$@fysnet.net>
On 25/02/2024 20.49, benlunt@fysnet.net wrote:
> Since Windows text files use CRLFs for all \n, the Windows version of QEMU
> inserts a CR in the PCAP stream when a LF is encountered when using USB PCAP
> files. This is due to the fact that the PCAP file is opened as TEXT instead
> of BINARY.
>
> To show an example, when using a very common protocol to USB disks, the BBB
> protocol uses a 10-byte command packet. For example, the READ_CAPACITY(10)
> command will have a command block length of 10 (0xA). When this 10-byte
> command (part of the 31-byte CBW) is placed into the PCAP file, the Windows
> file manager inserts a 0xD before the 0xA, turning the 31-byte CBW into a
> 32-byte CBW.
>
> Actual CBW:
> 0040 55 53 42 43 01 00 00 00 08 00 00 00 80 00 0a 25 USBC...........%
> 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
>
> PCAP CBW
> 0040 55 53 42 43 01 00 00 00 08 00 00 00 80 00 0d 0a USBC............
> 0050 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 %..............
>
> I believe simply opening the PCAP file as BINARY instead of TEXT will fix
> this issue.
>
> Resolves: https://bugs.launchpad.net/qemu/+bug/2054889
> Signed-off-by: Benjamin David Lunt <benlunt@fysnet.net>
> ---
> hw/usb/bus.c | 2 +-
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff -u a/hw/usb/bus.c b/hw/usb/bus.c
> --- a/hw/usb/bus.c
> +++ b/hw/usb/bus.c
> @@ -273,13 +273,13 @@
> }
>
> if (dev->pcap_filename) {
> - int fd = qemu_open_old(dev->pcap_filename, O_CREAT | O_WRONLY |
> O_TRUNC, 0666);
> + int fd = qemu_open_old(dev->pcap_filename, O_CREAT | O_WRONLY |
> O_TRUNC | O_BINARY, 0666);
Hi Benjamin!
Thanks for the patch! Since it's rather a trivial patch and our USB
maintainer Gerd is pretty much busy with other stuff right now, I went ahead
and put it in my current pull request.
Two things to notice: First, something along the way (likely your mail
program) added a line break after the "O_WRONLY |" in the above two lines,
so I had to undo that change manually before I was able to apply the patch
... please try to use "git send-email" for sending patches, then such things
don't happen.
And second, please use the scripts/checkpatch.pl script to check your
patches - it was complaining about a line getting too long here, so I went
ahead and fixed that, too (i.e. no need to resend, just a FYI for future
patches).
Thanks,
Thomas
> if (fd < 0) {
> error_setg(errp, "open %s failed", dev->pcap_filename);
> usb_qdev_unrealize(qdev);
> return;
> }
> - dev->pcap = fdopen(fd, "w");
> + dev->pcap = fdopen(fd, "wb");
> usb_pcap_init(dev->pcap);
> }
> }
>
>
>
prev parent reply other threads:[~2024-03-01 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 19:49 [PATCH] hw/us/bus.c PCAP adding 0xA in Windows version benlunt
2024-02-25 21:55 ` BALATON Zoltan
2024-03-01 8:18 ` Thomas Huth [this message]
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=56e58fe0-476c-4daf-b61c-3fc24d7623a5@redhat.com \
--to=thuth@redhat.com \
--cc=benlunt@fysnet.net \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).