qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>, Jason Wang <jasowang@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Cc: Bin Meng <bin.meng@windriver.com>
Subject: Re: [RFC PATCH 1/3] net: Pad short frames to minimum size (60 bytes)
Date: Fri, 26 Feb 2021 11:29:07 +0100	[thread overview]
Message-ID: <b9c3f883-7365-f30c-0b22-15b5e089268a@redhat.com> (raw)
In-Reply-To: <1614333786-74258-2-git-send-email-bmeng.cn@gmail.com>

On 2/26/21 11:03 AM, Bin Meng wrote:
> From: Bin Meng <bin.meng@windriver.com>
> 
> The minimum Ethernet frame length is 60 bytes, and we should pad
> frames whose length is smaller to the minimum size.
> 
> This commit fixes the issue as seen with various ethernet models,
> that ARP requests get dropped, preventing the guest from becoming
> visible on the network.

Is it also used in commit 18995b9808d ("Send a RARP packet after
migration.")?

> The following 2 commits that attempted to workaround this issue
> in e1000 and vmxenet3 before, should be reverted.
> 
>   commit 78aeb23eded2 ("e1000: Pad short frames to minimum size (60 bytes)")
>   commit 40a87c6c9b11 ("vmxnet3: Pad short frames to minimum size (60 bytes)")
> 
> Signed-off-by: Bin Meng <bin.meng@windriver.com>
> ---
> 
>  net/net.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/net/net.c b/net/net.c
> index b038370..34004da 100644
> --- a/net/net.c
> +++ b/net/net.c
> @@ -638,6 +638,7 @@ static ssize_t qemu_send_packet_async_with_flags(NetClientState *sender,
>                                                   NetPacketSent *sent_cb)
>  {
>      NetQueue *queue;
> +    uint8_t min_buf[60];

Can you add a definition instead of a magic value?
Maybe ETH_FRAME_MIN_LEN in "net/eth.h"?

>      int ret;
>  
>  #ifdef DEBUG_NET
> @@ -649,6 +650,14 @@ static ssize_t qemu_send_packet_async_with_flags(NetClientState *sender,
>          return size;
>      }
>  
> +    /* Pad to minimum Ethernet frame length */
> +    if (size < sizeof(min_buf)) {
> +        memcpy(min_buf, buf, size);
> +        memset(&min_buf[size], 0, sizeof(min_buf) - size);
> +        buf = min_buf;
> +        size = sizeof(min_buf);
> +    }
> +
>      /* Let filters handle the packet first */
>      ret = filter_receive(sender, NET_FILTER_DIRECTION_TX,
>                           sender, flags, buf, size, sent_cb);
> 



  reply	other threads:[~2021-02-26 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 10:03 [RFC PATCH 0/3] net: Pad short frames to minimum size (60 bytes) Bin Meng
2021-02-26 10:03 ` [RFC PATCH 1/3] " Bin Meng
2021-02-26 10:29   ` Philippe Mathieu-Daudé [this message]
2021-02-26 11:51     ` Mark Cave-Ayland
2021-02-26 18:57   ` Peter Maydell
2021-02-27  2:00     ` Bin Meng
2021-02-26 10:03 ` [RFC PATCH 2/3] Revert "e1000: Pad short frames to minimum size (60 bytes)" Bin Meng
2021-02-26 10:03 ` [RFC PATCH 3/3] Revert "vmxnet3: " Bin Meng

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=b9c3f883-7365-f30c-0b22-15b5e089268a@redhat.com \
    --to=philmd@redhat.com \
    --cc=bin.meng@windriver.com \
    --cc=bmeng.cn@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).