qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Pinnock <1914117@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1914117] Re: Short files returned via FTP on Qemu with various architectures and OSes
Date: Wed, 10 Feb 2021 11:14:46 -0000	[thread overview]
Message-ID: <161295568661.28988.4275406897326730736.malone@soybean.canonical.com> (raw)
In-Reply-To: 161221293549.4659.2173832767419505412.malonedeb@chaenomeles.canonical.com

This is NOT a fix but we can get working FTPs again with this patch -
narrowing into where the problem is. Looks like the behaviour of this
code is different on macOS to other OSes.

--- slirp.c.orig	2021-02-08 21:05:20.000000000 +0000
+++ slirp.c	2021-02-10 11:00:00.000000000 +0000
@@ -621,18 +621,7 @@
              * This will soread as well, so no need to
              * test for SLIRP_POLL_IN below if this succeeds
              */
-            if (revents & SLIRP_POLL_PRI) {
-               ret = sorecvoob(so);
-               if (ret < 0) {
-                   /* Socket error might have resulted in the socket being
-                     * removed, do not try to do anything more with it. */
-                    continue;
-                }
-            }
-            /*
-             * Check sockets for reading
-             */
-            else if (revents & 
+            if (revents & 
                      (SLIRP_POLL_IN | SLIRP_POLL_HUP | SLIRP_POLL_ERR)) {
                 /*
                  * Check for incoming connections

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1914117

Title:
  Short files returned via FTP on Qemu with various architectures and
  OSes

Status in QEMU:
  New

Bug description:
  
  Qemu 5.2 on Mac OS X Big Sur.

  I originally thought that it might be caused by the home-brew version of Qemu, but this evening I have removed the brew edition and compiled from scratch (using Ninja & Xcode compiler). 
  Still getting the same problem,.

  On the following architectures: 
  arm64, amd64 and sometimes i386 running NetBSD host OS; 
  i386 running OpenBSD host OS:

  I have seen a consistent problem with FTP returning short files. The
  file will be a couple of bytes too short. I do not believe this is a
  problem with the OS. Downloading the perl source code from CPAN does
  not work properly, nor does downloading bind from isc. I've tried this
  on different architectures as above.

  (Qemu 4.2 on Ubuntu/x86_64 with NetBSD/i386 seems to function fine. My
  gut feel is there is something not right on the Mac OS version of Qemu
  or a bug in 5.2 - obviously in the network layer somewhere. If you
  have anything you want me to try, please let me know - happy to help
  get a resolution.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1914117/+subscriptions


  parent reply	other threads:[~2021-02-10 11:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 20:55 [Bug 1914117] [NEW] Short files returned via FTP on Qemu with various architectures and OSes Chris Pinnock
2021-02-02  5:24 ` [Bug 1914117] " Thomas Huth
2021-02-02  6:58   ` [Bug 1914117] " Chris Pinnock
2021-02-02  6:59 ` [Bug 1914117] " Chris Pinnock
2021-02-02 21:28 ` Chris Pinnock
2021-02-02 21:30 ` Chris Pinnock
2021-02-03 13:21 ` Chris Pinnock
2021-02-07 18:10 ` Chris Pinnock
2021-02-10 11:14 ` Chris Pinnock [this message]
2021-02-10 12:26 ` Chris Pinnock
2021-02-11 15:49 ` Chris Pinnock
2021-02-22 16:57 ` Thomas Huth
2021-03-01 19:23 ` Chris Pinnock
2021-05-15 10:49 ` Thomas Huth
2021-05-15 12:29   ` Chris Pinnock
2021-06-21  5:04 ` Thomas Huth
2021-08-21  6:48 ` Thomas Huth
2021-08-25  7:18 ` Thomas Huth
2021-09-11 13:30   ` [Bug 1914117] " Chris Pinnock

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=161295568661.28988.4275406897326730736.malone@soybean.canonical.com \
    --to=1914117@bugs.launchpad.net \
    --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).