public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>
Subject: Re: [PATCH] net: pad virtio_net_ff_cap_data
Date: Wed, 19 Nov 2025 03:33:14 -0500	[thread overview]
Message-ID: <20251119033147-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CY8PR12MB7195A3E4ED0AF590BEB0A629DCD7A@CY8PR12MB7195.namprd12.prod.outlook.com>

On Wed, Nov 19, 2025 at 08:29:48AM +0000, Parav Pandit wrote:
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: 19 November 2025 01:54 PM
> > 
> > struct virtio_net_ff_cap_data has 4 byte fields but the size is not a multiple of
> > 4.  drivers can easily get it wrong since compilers tend to add padding to align
> > such structures.
> > 
> > Since we are always allowed to pad or truncate admin commands, let's do just
> > that here.
> > 
> > Fixes: 899bb0c ("virtio-net: Add flow filter capability")
> > Cc: "Parav Pandit" <parav@nvidia.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >  device-types/net/description.tex | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/device-types/net/description.tex b/device-
> > types/net/description.tex
> > index 9833d16..0b4fcac 100644
> > --- a/device-types/net/description.tex
> > +++ b/device-types/net/description.tex
> > @@ -3055,6 +3055,7 @@ \subsubsection{Flow filter}\label{sec:Device Types
> > / Network Device / Device Ope
> >          le32 rules_per_group_limit;
> >          u8 last_rule_priority;
> >          u8 selectors_per_classifier_limit;
> > +        u8 reserved[2];
> >  };
> >  \end{lstlisting}
> > 
> Thanks for the fix.
> We should align to the 8B boundary instead of 4B.

We can but we don't have to. We need to align on the
size of the largest field in the structure. This one
only has 4B fields.


> It should be reserved[6].
> 
> > @@ -3071,6 +3072,8 @@ \subsubsection{Flow filter}\label{sec:Device Types
> > / Network Device / Device Ope  \field{selectors_per_classifier_limit} is the
> > maximum number of selectors  that a classifier can have.
> > 
> > +\field{reserved} is reserved and set to zero.
> > +
> >  \subparagraph{VIRTIO_NET_FF_SELECTOR_CAP}
> >  \label{par:Device Types / Network Device / Device Operation / Flow filter /
> > Device and driver capabilities / VIRTIO-NET-FF-SELECTOR-CAP}
> > 
> > --
> > MST


  reply	other threads:[~2025-11-19  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  8:23 [PATCH] net: pad virtio_net_ff_cap_data Michael S. Tsirkin
2025-11-19  8:29 ` Parav Pandit
2025-11-19  8:33   ` Michael S. Tsirkin [this message]
2025-11-19  8:34   ` Michael S. Tsirkin
2025-11-19  9:38     ` Parav Pandit
2025-11-19  9:41       ` Michael S. Tsirkin

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=20251119033147-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=parav@nvidia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox