All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Sathya Perla <sathya.perla@avagotech.com>, netdev@vger.kernel.org
Subject: Re: [net-next PATCH 05/10] be2net: log digital signature errors while flashing FW image
Date: Thu, 24 Dec 2015 16:23:07 +0300	[thread overview]
Message-ID: <567BF1BB.50201@cogentembedded.com> (raw)
In-Reply-To: <1450949192-4574-6-git-send-email-sathya.perla@avagotech.com>

Hello.

On 12/24/2015 12:26 PM, Sathya Perla wrote:

> From: Suresh Reddy <suresh.reddy@avagotech.com>
>
>  From FW version 11.0 onwards, the FW supports a new "secure mode" feature
> (based on a jumper setting on the adapter.) In this mode, the FW image when
> flashed is authenticated with a digital signature. This patch logs
> appropriate error messages and return a status to ethtool when errors
> relating to FW image authentication occur.
>
> Signed-off-by: Suresh Reddy <suresh.reddy@avagotech.com>
> Signed-off-by: Sathya Perla <sathya.perla@avagotech.com>
> ---
>   drivers/net/ethernet/emulex/benet/be_cmds.c | 11 +++++++++++
>   drivers/net/ethernet/emulex/benet/be_cmds.h |  4 +++-
>   2 files changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/emulex/benet/be_cmds.c b/drivers/net/ethernet/emulex/benet/be_cmds.c
> index da3b398..6fb7873 100644
> --- a/drivers/net/ethernet/emulex/benet/be_cmds.c
> +++ b/drivers/net/ethernet/emulex/benet/be_cmds.c
> @@ -2959,6 +2959,17 @@ flash:
>   		} else if (status) {
>   			dev_err(dev, "Flashing section type 0x%x failed\n",
>   				img_type);
> +			if (addl_status(status) ==
> +			    MCC_ADDL_STATUS_MISSING_SIGNATURE) {
> +				dev_err(dev,
> +					"Digital signature missing in FW\n");
> +				return -EINVAL;
> +			} else if (addl_status(status) ==
> +				   MCC_ADDL_STATUS_INVALID_SIGNATURE) {
> +				dev_err(dev,
> +					"Invalid digital signature in FW\n");
> +				return -EINVAL;
> +			}

    Asks to be a *switch* statement.

[...]

MBR, Sergei

  reply	other threads:[~2015-12-24 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24  9:26 [net-next PATCH 00/10] be2net: patch set Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 01/10] be2net: fix VF link state transition from disabled to auto Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 02/10] be2net: avoid configuring VEPA mode on BE3 Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 03/10] be2net: cleanup FW flash image related macro defines Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 04/10] be2net: move FW flash cmd code to be_cmds.c Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 05/10] be2net: log digital signature errors while flashing FW image Sathya Perla
2015-12-24 13:23   ` Sergei Shtylyov [this message]
2015-12-24  9:26 ` [net-next PATCH 06/10] be2net: remove a line of code that has no effect Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 07/10] be2net: remove unused error variables Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 08/10] be2net: fix port-res desc query of GET_PROFILE_CONFIG FW cmd Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 09/10] be2net: support ethtool get-dump option Sathya Perla
2015-12-24  9:26 ` [net-next PATCH 10/10] be2net: bump up the driver version to 11.0.0.0 Sathya Perla

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=567BF1BB.50201@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=netdev@vger.kernel.org \
    --cc=sathya.perla@avagotech.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 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.