linux-aspeed.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v7] Add payload to be 32-bit aligned to fix dropped packets
Date: Thu, 18 Nov 2021 09:14:00 -0800	[thread overview]
Message-ID: <ad44434c-0356-701e-d355-174efc1917b5@gmail.com> (raw)
In-Reply-To: <20211118160301.GA19542@gmail.com>



On 11/18/21 8:03 AM, Kumar Thangavel wrote:
> Update NC-SI command handler (both standard and OEM) to take into
> account of payload paddings in allocating skb (in case of payload
> size is not 32-bit aligned).
> 
> The checksum field follows payload field, without taking payload
> padding into account can cause checksum being truncated, leading to
> dropped packets.
> 

Patch title should start with a prefix, identifying which layer/driver is
involved.

Probably in this case

net/ncsi: Add payload to be 32-bit aligned to fix dropped packets

> Fixes: fb4ee67529ff ("net/ncsi: Add NCSI OEM command support")
> Signed-off-by: Kumar Thangavel <thangavel.k@hcl.com>
> Acked-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
> Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
> 
> ---
>   v7:
>    - Updated padding_bytes as const static int variable
> 
>   v6:
>    - Updated type of padding_bytes variable
>    - Updated type of payload
>    - Seperated variable declarations and code
> 
>   v5:
>    - Added Fixes tag
>    - Added const variable for padding_bytes
> 
>   v4:
>    - Used existing macro for max function
> 
>   v3:
>    - Added Macro for MAX
>    - Fixed the missed semicolon
> 
>   v2:
>    - Added NC-SI spec version and section
>    - Removed blank line
>    - corrected spellings
> 
>   v1:
>    - Initial draft
> 
> ---
> ---
>  net/ncsi/ncsi-cmd.c | 24 ++++++++++++++++--------
>  1 file changed, 16 insertions(+), 8 deletions(-)
> 
> diff --git a/net/ncsi/ncsi-cmd.c b/net/ncsi/ncsi-cmd.c
> index ba9ae482141b..9a6f10f4833e 100644
> --- a/net/ncsi/ncsi-cmd.c
> +++ b/net/ncsi/ncsi-cmd.c
> @@ -18,6 +18,8 @@
>  #include "internal.h"
>  #include "ncsi-pkt.h"
>  
> +const static int padding_bytes = 26;

It would be nice to have some kind of reference, to explain
what is this magic value.

Moving the comment [1] here might make sense.


> +
>  u32 ncsi_calculate_checksum(unsigned char *data, int len)
>  {
>  	u32 checksum = 0;
> @@ -213,12 +215,17 @@ static int ncsi_cmd_handler_oem(struct sk_buff *skb,
>  {
>  	struct ncsi_cmd_oem_pkt *cmd;
>  	unsigned int len;
> +	int payload;

[1] This comment could be moved before @padding_bytes

> +	/* NC-SI spec DSP_0222_1.2.0, section 8.2.2.2
> +	 * requires payload to be padded with 0 to
> +	 * 32-bit boundary before the checksum field.
> +	 * Ensure the padding bytes are accounted for in
> +	 * skb allocation
> +	 */
>  
> +	payload = ALIGN(nca->payload, 4);
>  	len = sizeof(struct ncsi_cmd_pkt_hdr) + 4;
> -	if (nca->payload < 26)
> -		len += 26;
> -	else
> -		len += nca->payload;
> +	len += max(payload, padding_bytes);
>  
>  	cmd = skb_put_zero(skb, len);
>  	memcpy(&cmd->mfr_id, nca->data, nca->payload);
> @@ -272,6 +279,7 @@ static struct ncsi_request *ncsi_alloc_command(struct ncsi_cmd_arg *nca)
>  	struct net_device *dev = nd->dev;
>  	int hlen = LL_RESERVED_SPACE(dev);
>  	int tlen = dev->needed_tailroom;
> +	int payload;
>  	int len = hlen + tlen;
>  	struct sk_buff *skb;
>  	struct ncsi_request *nr;
> @@ -281,14 +289,14 @@ static struct ncsi_request *ncsi_alloc_command(struct ncsi_cmd_arg *nca)
>  		return NULL;
>  
>  	/* NCSI command packet has 16-bytes header, payload, 4 bytes checksum.
> +	 * Payload needs padding so that the checksum field following payload is
> +	 * aligned to 32-bit boundary.
>  	 * The packet needs padding if its payload is less than 26 bytes to
>  	 * meet 64 bytes minimal ethernet frame length.
>  	 */
>  	len += sizeof(struct ncsi_cmd_pkt_hdr) + 4;
> -	if (nca->payload < 26)
> -		len += 26;
> -	else
> -		len += nca->payload;
> +	payload = ALIGN(nca->payload, 4);
> +	len += max(payload, padding_bytes);
>  
>  	/* Allocate skb */
>  	skb = alloc_skb(len, GFP_ATOMIC);
> 

  reply	other threads:[~2021-11-18 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 16:03 [PATCH v7] Add payload to be 32-bit aligned to fix dropped packets Kumar Thangavel
2021-11-18 17:14 ` Eric Dumazet [this message]
2021-11-19  8:15   ` Kumar Thangavel
2021-11-19  3:15 ` kernel test robot
2021-11-19  6:32 ` Jakub Kicinski
2021-11-19  8:14   ` Kumar Thangavel
  -- strict thread matches above, loose matches on Subject: below --
2021-11-18 15:33 Kumar Thangavel

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=ad44434c-0356-701e-d355-174efc1917b5@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=linux-aspeed@lists.ozlabs.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).