All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: virtio-comment@lists.linux.dev, Parav Pandit <parav@nvidia.com>
Subject: Re: [PATCH] virtio-net: Fix receive buffer size typo
Date: Fri, 7 Feb 2025 06:07:18 -0500	[thread overview]
Message-ID: <20250207060551-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250207-v1-4-topic-virtio-net-receive-buffer-fix-v1-1-efcef167d6bc@pengutronix.de>

On Fri, Feb 07, 2025 at 08:48:47AM +0100, Steffen Trumtrar wrote:
> The commit 00806815385340dd411cc67df3f6837935bb5e26 introduced a slight
> typo in the struct virtio_net_hdr size calculation depending on
> VIRTIO_NET_F_HASH_REPORT negotiation.
> 
> Without VIRTIO_NET_F_HASH_REPORT the struct is smaller than with the
> feature. This mix up only occurs in one instance; sizes are correct in
> all other occurences.
> 
> Fix this typo.
> 
> Fixes: 008068153853 ("virtio-net: Fix receive buffer size calculation text")
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> Reviewed-by: Parav Pandit <parav@nvidia.com>


Thanks!

Acked-by: Michael S. Tsirkin <mst@redhat.com>

Can you follow the process outlined here:
https://github.com/oasis-tcs/virtio-spec/blob/master/README.md#use-of-github-issues
to get it merged, or do you need help with that?


> ---
>  device-types/net/description.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/device-types/net/description.tex b/device-types/net/description.tex
> index 4e4ffdb6e04e346af491edf65886fa096e506abc..08736b6804eafb303a5cfb2f27ec200cec8bd942 100644
> --- a/device-types/net/description.tex
> +++ b/device-types/net/description.tex
> @@ -789,10 +789,10 @@ \subsubsection{Setting Up Receive Buffers}\label{sec:Device Types / Network Devi
>  the IPv6 header, plus 65535 bytes of maximum IPv6 payload including any
>  extension header), otherwise 1514 bytes.
>  When VIRTIO_NET_F_HASH_REPORT is not negotiated, the required receive buffer
> -size is either 65601 or 1526 bytes accounting for 20 bytes of
> +size is either 65601 or 1526 bytes accounting for 12 bytes of
>  \field{struct virtio_net_hdr} followed by receive packet.
>  When VIRTIO_NET_F_HASH_REPORT is negotiated, the required receive buffer
> -size is either 65609 or 1534 bytes accounting for 12 bytes of
> +size is either 65609 or 1534 bytes accounting for 20 bytes of
>  \field{struct virtio_net_hdr} followed by receive packet.
>  
>  \drivernormative{\paragraph}{Setting Up Receive Buffers}{Device Types / Network Device / Device Operation / Setting Up Receive Buffers}
> 
> ---
> base-commit: b2990c8a6642e696d6f269d1db991b2c928d3a9f
> change-id: 20250207-v1-4-topic-virtio-net-receive-buffer-fix-b6487b58813c
> 
> Best regards,
> -- 
> Steffen Trumtrar <s.trumtrar@pengutronix.de>
> 


  reply	other threads:[~2025-02-07 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07  7:48 [PATCH] virtio-net: Fix receive buffer size typo Steffen Trumtrar
2025-02-07 11:07 ` Michael S. Tsirkin [this message]
2025-02-17  7:00 ` Steffen Trumtrar

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=20250207060551-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=s.trumtrar@pengutronix.de \
    --cc=virtio-comment@lists.linux.dev \
    /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.