netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Eran Ben Elisha <eranbe@mellanox.com>
Cc: netdev@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Chris Preimesberger <chrisp@transition.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	Vidya Sagar Ravipati <vidya@cumulusnetworks.com>
Subject: Re: [PATCH ethtool] ethtool: Fix uninitialized variable use at qsfp dump
Date: Thu, 27 Sep 2018 18:08:17 +0200	[thread overview]
Message-ID: <20180927160817.GH12979@lunn.ch> (raw)
In-Reply-To: <1538056115-6677-1-git-send-email-eranbe@mellanox.com>

On Thu, Sep 27, 2018 at 04:48:35PM +0300, Eran Ben Elisha wrote:
> Struct sff_diags can be used uninitialized at sff8636_show_dom, this
> caused the tool to show unreported fields (supports_alarms) by the lower
> level driver.
> 
> Fixes: a5e73bb05ee4 ("ethtool:QSFP Plus/QSFP28 Diagnostics Information Support")
> Signed-off-by: Eran Ben Elisha <eranbe@mellanox.com>
> ---
>  qsfp.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/qsfp.c b/qsfp.c
> index 32e195d12dc0..d196aa1753de 100644
> --- a/qsfp.c
> +++ b/qsfp.c
> @@ -671,7 +671,7 @@ static void sff8636_dom_parse(const __u8 *id, struct sff_diags *sd)
>  
>  static void sff8636_show_dom(const __u8 *id, __u32 eeprom_len)
>  {
> -	struct sff_diags sd;
> +	struct sff_diags sd = {0};
>  	char *rx_power_string = NULL;
>  	char power_string[MAX_DESC_SIZE];
>  	int i;

Hi Erin

I wonder if similar bugs happen in sfpdiag.c?

void sff8472_show_all(const __u8 *id)
{
        struct sff_diags sd;
        char *rx_power_string = NULL;
        int i;

sd is also on the stack and not initialised. Could you expand your
patch to also clear this one as well, just to be safe.

Thanks
	Andrew

  reply	other threads:[~2018-09-27 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 13:48 [PATCH ethtool] ethtool: Fix uninitialized variable use at qsfp dump Eran Ben Elisha
2018-09-27 16:08 ` Andrew Lunn [this message]
2018-10-02  7:17   ` Eran Ben Elisha

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=20180927160817.GH12979@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=chrisp@transition.com \
    --cc=eranbe@mellanox.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=vidya@cumulusnetworks.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;
as well as URLs for NNTP newsgroup(s).