public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, oferh@marvell.com
Subject: Re: [PATCH] crypto: inside-secure: fix packed bit-field result descriptor
Date: Mon, 04 Jul 2022 09:26:29 +0200	[thread overview]
Message-ID: <165691958960.3764.6967842126015044710@kwain> (raw)
In-Reply-To: <20220702071426.1915429-1-oferh@marvell.com>

Hi Ofer,

Quoting oferh@marvell.com (2022-07-02 09:14:26)
> From: Ofer Heifetz <oferh@marvell.com>
> 
> When mixing bit-field and none bit-filed in packed struct the
> none bit-field starts at a distinct memory location, thus adding
> an additional byte to the overall structure which is used in
> memory zero-ing and other configuration calculations.
> 
> Fix this by removing the none bit-field that has a following
> bit-field.
> 
> Signed-off-by: Ofer Heifetz <oferh@marvell.com>

Nice catch!

Note: since those fields were not used before and IIRC the below result
struct size is set dynamically (the h/w doesn't expect a fixed size)
this doesn't need to be backported to stable trees. Can't test it on
real h/w though.

Acked-by: Antoine Tenart <atenart@kernel.org>

Thanks!

> ---
>  drivers/crypto/inside-secure/safexcel.h | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/crypto/inside-secure/safexcel.h b/drivers/crypto/inside-secure/safexcel.h
> index ce1e611a163e..797ff91512e0 100644
> --- a/drivers/crypto/inside-secure/safexcel.h
> +++ b/drivers/crypto/inside-secure/safexcel.h
> @@ -497,15 +497,15 @@ struct result_data_desc {
>         u32 packet_length:17;
>         u32 error_code:15;
>  
> -       u8 bypass_length:4;
> -       u8 e15:1;
> -       u16 rsvd0;
> -       u8 hash_bytes:1;
> -       u8 hash_length:6;
> -       u8 generic_bytes:1;
> -       u8 checksum:1;
> -       u8 next_header:1;
> -       u8 length:1;
> +       u32 bypass_length:4;
> +       u32 e15:1;
> +       u32 rsvd0:16;
> +       u32 hash_bytes:1;
> +       u32 hash_length:6;
> +       u32 generic_bytes:1;
> +       u32 checksum:1;
> +       u32 next_header:1;
> +       u32 length:1;
>  
>         u16 application_id;
>         u16 rsvd1;
> -- 
> 2.25.1
> 

  reply	other threads:[~2022-07-04  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02  7:14 [PATCH] crypto: inside-secure: fix packed bit-field result descriptor oferh
2022-07-04  7:26 ` Antoine Tenart [this message]
2022-07-04  8:27   ` [EXT] " Ofer Heifetz
2022-07-08  8:02 ` Herbert Xu

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=165691958960.3764.6967842126015044710@kwain \
    --to=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=oferh@marvell.com \
    /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