From: Dan Carpenter <dan.carpenter@oracle.com>
To: Camylla Goncalves Cantanheide <c.cantanheide@gmail.com>
Cc: gregkh@linuxfoundation.org, navid.emamdoost@gmail.com,
sylphrenadin@gmail.com, nishkadg.linux@gmail.com,
stephen@brennan.io, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, lkcamp@lists.libreplanetbr.org
Subject: Re: [PATCH 1/2] staging: rtl8192u: Refactoring setKey function
Date: Tue, 14 Apr 2020 15:33:26 +0300 [thread overview]
Message-ID: <20200414123326.GG1163@kadam> (raw)
In-Reply-To: <20200413030129.861-1-c.cantanheide@gmail.com>
On Mon, Apr 13, 2020 at 03:01:28AM +0000, Camylla Goncalves Cantanheide wrote:
> Changes of the local variable value and
> modification in the seletive repetition structure.
>
This changelog isn't totally clear why you're doing this. Just say:
"I am refactorying setKey() to make it more clear. I have unrolled the
first two iterations through the loop. This patch will not change
runtime."
So long as it's clear what you're trying to do and why, that's the
important thing with a commit message.
> Signed-off-by: Camylla Goncalves Cantanheide <c.cantanheide@gmail.com>
> ---
> drivers/staging/rtl8192u/r8192U_core.c | 52 ++++++++++++--------------
> 1 file changed, 24 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/staging/rtl8192u/r8192U_core.c b/drivers/staging/rtl8192u/r8192U_core.c
> index 9b8d85a4855d..87c02aee3854 100644
> --- a/drivers/staging/rtl8192u/r8192U_core.c
> +++ b/drivers/staging/rtl8192u/r8192U_core.c
> @@ -4880,7 +4880,7 @@ void EnableHWSecurityConfig8192(struct net_device *dev)
> void setKey(struct net_device *dev, u8 entryno, u8 keyindex, u16 keytype,
> u8 *macaddr, u8 defaultkey, u32 *keycontent)
> {
> - u32 target_command = 0;
> + u32 target_command = CAM_CONTENT_COUNT * entryno | BIT(31) | BIT(16);
> u32 target_content = 0;
> u16 us_config = 0;
> u8 i;
> @@ -4890,39 +4890,35 @@ void setKey(struct net_device *dev, u8 entryno, u8 keyindex, u16 keytype,
>
> RT_TRACE(COMP_SEC,
> "====>to %s, dev:%p, EntryNo:%d, KeyIndex:%d, KeyType:%d, MacAddr%pM\n",
> - __func__, dev, entryno, keyindex, keytype, macaddr);
> + __func__, dev, entryno, keyindex, keytype, macaddr);
Do this white space change in a separate patch.
>
> if (defaultkey)
> us_config |= BIT(15) | (keytype << 2);
> else
> us_config |= BIT(15) | (keytype << 2) | keyindex;
>
> - for (i = 0; i < CAM_CONTENT_COUNT; i++) {
> - target_command = i + CAM_CONTENT_COUNT * entryno;
> - target_command |= BIT(31) | BIT(16);
> -
> - if (i == 0) { /* MAC|Config */
> - target_content = (u32)(*(macaddr + 0)) << 16 |
> - (u32)(*(macaddr + 1)) << 24 |
> - (u32)us_config;
> -
> - write_nic_dword(dev, WCAMI, target_content);
> - write_nic_dword(dev, RWCAM, target_command);
> - } else if (i == 1) { /* MAC */
> - target_content = (u32)(*(macaddr + 2)) |
> - (u32)(*(macaddr + 3)) << 8 |
> - (u32)(*(macaddr + 4)) << 16 |
> - (u32)(*(macaddr + 5)) << 24;
> - write_nic_dword(dev, WCAMI, target_content);
> - write_nic_dword(dev, RWCAM, target_command);
> - } else {
> - /* Key Material */
> - if (keycontent) {
> - write_nic_dword(dev, WCAMI,
> - *(keycontent + i - 2));
> - write_nic_dword(dev, RWCAM, target_command);
> - }
> - }
> + target_content = macaddr[0] << 16 |
> + macaddr[0] << 24 |
> + (u32)us_config;
> +
> + write_nic_dword(dev, WCAMI, target_content);
> + write_nic_dword(dev, RWCAM, target_command++);
> +
> + /* MAC */
> + target_content = macaddr[2] |
> + macaddr[3] << 8 |
> + macaddr[4] << 16 |
> + macaddr[5] << 24;
> + write_nic_dword(dev, WCAMI, target_content);
> + write_nic_dword(dev, RWCAM, target_command++);
> +
> + /* Key Material */
> + if (!keycontent)
> + return;
> +
> + for (i = 2; i < CAM_CONTENT_COUNT; i++) {
> + write_nic_dword(dev, WCAMI, *keycontent++);
This code was wrong in the original as well, but now that I see the bug
let's fix it. CAM_CONTENT_COUNT is 8. 8 - 2 = 6. We are writing 6
u32 variables to write_nic_dword(). But the *keycontent buffer only has
4 u32 variables so it is a buffer overflow.
> + write_nic_dword(dev, RWCAM, target_command++);
> }
> }
regards,
dan carpenter
next prev parent reply other threads:[~2020-04-14 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 3:01 [PATCH 1/2] staging: rtl8192u: Refactoring setKey function Camylla Goncalves Cantanheide
2020-04-13 3:01 ` [PATCH 2/2] staging: rtl8192u: Renames variables in " Camylla Goncalves Cantanheide
2020-04-13 12:50 ` Greg KH
2020-04-13 12:50 ` [PATCH 1/2] staging: rtl8192u: Refactoring " Greg KH
2020-04-13 15:39 ` Joe Perches
2020-04-14 12:33 ` Dan Carpenter [this message]
2020-04-14 16:01 ` Joe Perches
2020-04-14 18:32 ` Dan Carpenter
[not found] ` <CAG3pEr+huVACoP7sTMALYfE46dc+D8DdGPF0ky6EShd4eXD9eg@mail.gmail.com>
2020-04-15 3:09 ` Joe Perches
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=20200414123326.GG1163@kadam \
--to=dan.carpenter@oracle.com \
--cc=c.cantanheide@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=navid.emamdoost@gmail.com \
--cc=nishkadg.linux@gmail.com \
--cc=stephen@brennan.io \
--cc=sylphrenadin@gmail.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