From: Andrew Lunn <andrew@lunn.ch>
To: Luo bin <luobin9@huawei.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, luoxianjun@huawei.com,
yin.yinshi@huawei.com, cloud.wangxiaoyun@huawei.com
Subject: Re: [PATCH net-next v1 5/5] hinic: add support to get eeprom information
Date: Sat, 20 Jun 2020 18:00:38 +0200 [thread overview]
Message-ID: <20200620160038.GQ304147@lunn.ch> (raw)
In-Reply-To: <20200620094258.13181-6-luobin9@huawei.com>
> +static int hinic_get_module_eeprom(struct net_device *netdev,
> + struct ethtool_eeprom *ee, u8 *data)
> +{
> + struct hinic_dev *nic_dev = netdev_priv(netdev);
> + u8 sfp_data[STD_SFP_INFO_MAX_SIZE];
sfp_data will contain whatever is on the stack.
> + u16 len;
> + int err;
> +
> + if (!ee->len || ((ee->len + ee->offset) > STD_SFP_INFO_MAX_SIZE))
> + return -EINVAL;
> +
> + memset(data, 0, ee->len);
This clears what you are going to return.
> +
> + err = hinic_get_sfp_eeprom(nic_dev->hwdev, sfp_data, &len);
Upto len bytes of sfp_data now contain useful data. The rest of
sfp_data is still stack data.
> + if (err)
> + return err;
> +
> + memcpy(data, sfp_data + ee->offset, ee->len);
If len < ee->len, you have just returned to user space some stack data.
Andrew
next prev parent reply other threads:[~2020-06-20 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 9:42 [PATCH net-next v1 0/5] hinic: add some ethtool ops support Luo bin
2020-06-20 9:42 ` [PATCH net-next v1 1/5] hinic: add support to set and get pause params Luo bin
2020-06-20 9:42 ` [PATCH net-next v1 2/5] hinic: add support to set and get irq coalesce Luo bin
2020-06-22 22:07 ` Jakub Kicinski
2020-06-23 6:40 ` luobin (L)
2020-06-22 22:08 ` Jakub Kicinski
2020-06-23 6:41 ` luobin (L)
2020-06-20 9:42 ` [PATCH net-next v1 3/5] hinic: add self test support Luo bin
2020-06-20 9:42 ` [PATCH net-next v1 4/5] hinic: add support to identify physical device Luo bin
2020-06-20 9:42 ` [PATCH net-next v1 5/5] hinic: add support to get eeprom information Luo bin
2020-06-20 16:00 ` Andrew Lunn [this message]
2020-06-22 2:05 ` luobin (L)
2020-06-22 22:15 ` Jakub Kicinski
2020-06-23 6:48 ` luobin (L)
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=20200620160038.GQ304147@lunn.ch \
--to=andrew@lunn.ch \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luobin9@huawei.com \
--cc=luoxianjun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=yin.yinshi@huawei.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).