From: walter harms <wharms@bfs.de>
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
gregkh@linuxfoundation.org, yongjun_wei@trendmicro.com.cn,
jim.cromie@gmail.com, marcos.souza.org@gmail.com,
devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: rtl8712: avoid a useless call to memset().
Date: Wed, 05 Dec 2012 09:12:57 +0100 [thread overview]
Message-ID: <50BF0209.9080207@bfs.de> (raw)
In-Reply-To: <1354670522-27144-1-git-send-email-tipecaml@gmail.com>
Hi Cyril,
you patch is correct ..but being an advocate of defensive programming
i would say the original version especially since the number of bytes is small.
re,
wh
Am 05.12.2012 02:22, schrieb Cyril Roelandt:
> In r8711_wx_get_wap(), make sure we do not call memcpy() on a memory area that
> has just been zeroed by a call to memset().
>
> Signed-off-by: Cyril Roelandt <tipecaml@gmail.com>
> ---
> drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8712/rtl871x_ioctl_linux.c b/drivers/staging/rtl8712/rtl871x_ioctl_linux.c
> index 3a64790..2c73319 100644
> --- a/drivers/staging/rtl8712/rtl871x_ioctl_linux.c
> +++ b/drivers/staging/rtl8712/rtl871x_ioctl_linux.c
> @@ -1131,10 +1131,11 @@ static int r8711_wx_get_wap(struct net_device *dev,
> struct ndis_wlan_bssid_ex *pcur_bss = &pmlmepriv->cur_network.network;
>
> wrqu->ap_addr.sa_family = ARPHRD_ETHER;
> - memset(wrqu->ap_addr.sa_data, 0, ETH_ALEN);
> if (check_fwstate(pmlmepriv, _FW_LINKED |
> WIFI_ADHOC_MASTER_STATE|WIFI_AP_STATE)) {
> memcpy(wrqu->ap_addr.sa_data, pcur_bss->MacAddress, ETH_ALEN);
> + } else {
> + memset(wrqu->ap_addr.sa_data, 0, ETH_ALEN);
> }
> return 0;
> }
prev parent reply other threads:[~2012-12-05 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 1:22 Cyril Roelandt
2012-12-05 4:07 ` Larry Finger
2012-12-05 7:11 ` Dan Carpenter
2012-12-09 0:31 ` Cyril Roelandt
2012-12-10 8:55 ` Dan Carpenter
2012-12-05 8:12 ` walter harms [this message]
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=50BF0209.9080207@bfs.de \
--to=wharms@bfs.de \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jim.cromie@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=tipecaml@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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
Powered by JetHome