From: Ben Hutchings <bhutchings@solarflare.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
Hayes Wang <hayeswang@realtek.com>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH net-next 2/4] r8169: explicit firmware format check.
Date: Fri, 17 Jun 2011 22:13:20 +0100 [thread overview]
Message-ID: <1308345200.2831.31.camel@bwh-desktop> (raw)
In-Reply-To: <20110617193105.GB2287@electric-eye.fr.zoreil.com>
On Fri, 2011-06-17 at 21:31 +0200, Francois Romieu wrote:
> Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
> ---
> drivers/net/r8169.c | 54 +++++++++++++++++++++++++++++++++++++++-----------
> 1 files changed, 42 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
> index 3eeefe4..452db86 100644
> --- a/drivers/net/r8169.c
> +++ b/drivers/net/r8169.c
> @@ -669,6 +669,15 @@ struct rtl8169_private {
>
> struct rtl_fw {
> const struct firmware *fw;
> +
> +#define RTL_VER_SIZE 32
> +
> + char version[RTL_VER_SIZE];
> +
> + struct rtl_fw_phy_action {
> + __le32 *code;
> + size_t size;
> + } phy_action;
> } *rtl_fw;
> #define RTL_FIRMWARE_UNKNOWN ERR_PTR(-EAGAIN);
> };
> @@ -1230,7 +1239,7 @@ static void rtl8169_get_drvinfo(struct net_device *dev,
> strcpy(info->version, RTL8169_VERSION);
> strcpy(info->bus_info, pci_name(tp->pci_dev));
> strncpy(info->fw_version, IS_ERR_OR_NULL(rtl_fw) ? "N/A" :
> - rtl_lookup_firmware_name(tp), sizeof(info->fw_version) - 1);
> + rtl_fw->version, RTL_VER_SIZE);
You appear to ensure that rtl_fw->version is properly terminated, so I
would suggest:
BUILD_BUG_ON(sizeof(info->fw_version) < sizeof(rtl_fw->version));
strcpy(info->fw_version, IS_ERR_OR_NULL(rtl_fw) ? "N/A" : rtl_fw->version);
> }
>
> static int rtl8169_get_regs_len(struct net_device *dev)
> @@ -1744,21 +1753,42 @@ static void rtl_writephy_batch(struct rtl8169_private *tp,
> #define PHY_DELAY_MS 0xe0000000
> #define PHY_WRITE_ERI_WORD 0xf0000000
>
> -static void rtl_phy_write_fw(struct rtl8169_private *tp, struct rtl_fw *rtl_fw)
> +#define FW_OPCODE_SIZE sizeof(typeof(*((struct rtl_fw_phy_action *)0)->code))
> +
> +static bool rtl_fw_format_ok(struct rtl8169_private *tp, struct rtl_fw *rtl_fw)
> {
> const struct firmware *fw = rtl_fw->fw;
> - __le32 *phytable = (__le32 *)fw->data;
> + struct rtl_fw_phy_action *pa = &rtl_fw->phy_action;
> + bool rc = false;
> +
> + if (!(fw->size % FW_OPCODE_SIZE)) {
> + snprintf(rtl_fw->version, RTL_VER_SIZE, "%s",
> + rtl_lookup_firmware_name(tp));
strlcpy()
> + pa->code = (__le32 *)fw->data;
> + pa->size = fw->size / FW_OPCODE_SIZE;
> + }
> + rtl_fw->version[RTL_VER_SIZE - 1] = 0;
> +
> + rc = true;
> +
> + return rc;
> +}
[...]
This function is doing rather more than what its name suggests. And it
always returns true, so it doesn't actually do what its name suggests at
all.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-06-17 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 19:28 [PATCH net-next 0/4] Pull request for 'davem-next.r8169' branch Francois Romieu
2011-06-17 19:30 ` [PATCH net-next 1/4] r8169: move the firmware down into the device private data Francois Romieu
2011-06-17 19:31 ` [PATCH net-next 2/4] r8169: explicit firmware format check Francois Romieu
2011-06-17 21:13 ` Ben Hutchings [this message]
2011-06-17 22:11 ` Francois Romieu
2011-06-17 21:16 ` Ben Hutchings
2011-06-17 19:31 ` [PATCH net-next 3/4] r8169: support new firmware format Francois Romieu
2011-06-17 21:15 ` Ben Hutchings
2011-06-17 19:32 ` [PATCH net-next 4/4] r8169: check firmware content sooner Francois Romieu
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=1308345200.2831.31.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.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).