From: "Alexey V. Vissarionov" <gremlin@altlinux•org>
To: Simon Horman <simon.horman@corigine•com>
Cc: "Alexey V. Vissarionov" <gremlin@altlinux•org>,
"Arend van Spriel" <aspriel@gmail•com>,
"Franky Lin" <franky.lin@broadcom•com>,
"Hante Meuleman" <hante.meuleman@broadcom•com>,
"Kalle Valo" <kvalo@kernel•org>,
"David S. Miller" <davem@davemloft•net>,
"Eric Dumazet" <edumazet@google•com>,
"Jakub Kicinski" <kuba@kernel•org>,
"Paolo Abeni" <pabeni@redhat•com>,
"Alvin Šipraga" <alsi@bang-olufsen•dk>,
"Ahmad Fatoum" <a.fatoum@pengutronix•de>,
"Wataru Gohda" <wataru.gohda@cypress•com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix•de>,
"Wolfram Sang" <wsa+renesas@sang-engineering•com>,
"Pieter-Paul Giesberts" <pieter-paul.giesberts@broadcom•com>,
linux-wireless@vger•kernel.org,
brcm80211-dev-list.pdl@broadcom•com,
SHA-cyfmac-dev-list@infineon•com, netdev@vger•kernel.org,
lvc-project@linuxtesting•org
Subject: Re: [PATCH] wifi: brcmfmac: Fix allocation size
Date: Tue, 17 Jan 2023 14:54:30 +0300 [thread overview]
Message-ID: <20230117115430.GC15213@altlinux.org> (raw)
In-Reply-To: <Y8aCwr0BEi6zZEwO@corigine.com>
On 2023-01-17 12:13:06 +0100, Simon Horman wrote:
>> buf_size = sizeof(*rfi);
>> max_idx = reorder_data[BRCMF_RXREORDER_MAXIDX_OFFSET];
>> - buf_size += (max_idx + 1) * sizeof(pkt);
>> + buf_size += (max_idx + 1) * sizeof(struct sk_buff);
> This is followed by:
> rfi = kzalloc(buf_size, GFP_ATOMIC);
> ...
> rfi->pktslots = (struct sk_buff **)(rfi + 1);
> The type of rfi is struct brcmf_ampdu_rx_reorder, which
> looks like this:
> struct brcmf_ampdu_rx_reorder
> { struct sk_buff **pktslots; ... };
> And it looks to me that pkt is used as an array of
> (struct sk_buff *).
> So in all, it seems to me that the current code is correct.
So, the buf_size is a sum of sizeof(struct brcmf_ampdu_rx_reorder)
and size of array of pointers... and yes, this array is filled with
pointers: rfi->pktslots[rfi->cur_idx] = pkt;
Hmmm... looks correct. Sorry for bothering.
--
Alexey V. Vissarionov
gremlin ПРИ altlinux ТЧК org; +vii-cmiii-ccxxix-lxxix-xlii
GPG: 0D92F19E1C0DC36E27F61A29CD17E2B43D879005 @ hkp://keys.gnupg.net
next prev parent reply other threads:[~2023-01-17 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 10:45 [PATCH] wifi: brcmfmac: Fix allocation size Alexey V. Vissarionov
2023-01-17 11:05 ` Kalle Valo
2023-01-17 11:21 ` Alexey V. Vissarionov
2023-01-18 3:59 ` Kalle Valo
2023-01-17 11:13 ` Simon Horman
2023-01-17 11:54 ` Alexey V. Vissarionov [this message]
2023-01-17 13:56 ` Arend van Spriel
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=20230117115430.GC15213@altlinux.org \
--to=gremlin@altlinux$(echo .)org \
--cc=SHA-cyfmac-dev-list@infineon$(echo .)com \
--cc=a.fatoum@pengutronix$(echo .)de \
--cc=alsi@bang-olufsen$(echo .)dk \
--cc=aspriel@gmail$(echo .)com \
--cc=bigeasy@linutronix$(echo .)de \
--cc=brcm80211-dev-list.pdl@broadcom$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=franky.lin@broadcom$(echo .)com \
--cc=hante.meuleman@broadcom$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kvalo@kernel$(echo .)org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=lvc-project@linuxtesting$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pieter-paul.giesberts@broadcom$(echo .)com \
--cc=simon.horman@corigine$(echo .)com \
--cc=wataru.gohda@cypress$(echo .)com \
--cc=wsa+renesas@sang-engineering$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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