From: Michael Walle <mwalle@kernel.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Ajay Singh <ajay.kathat@microchip.com>,
stable@vger.kernel.org, heiko.thiery@gmail.com
Subject: Re: [PATCH] wifi: wilc1000: use vmm_table as array in wilc struct
Date: Fri, 13 Oct 2023 11:24:31 +0200 [thread overview]
Message-ID: <f615b0895135489a2555d898afdcfbfa@kernel.org> (raw)
In-Reply-To: <20231013-wilc1000_tx_oops-v1-1-3761beb9524d@bootlin.com>
Hi,
Am 2023-10-13 10:26, schrieb Alexis Lothoré:
> From: Ajay Singh <ajay.kathat@microchip.com>
>
> Enabling KASAN and running some iperf tests raises some memory issues
> with
> vmm_table:
>
> BUG: KASAN: slab-out-of-bounds in wilc_wlan_handle_txq+0x6ac/0xdb4
> Write of size 4 at addr c3a61540 by task wlan0-tx/95
>
> KASAN detects that we are writing data beyond range allocated to
> vmm_table.
> There is indeed a mismatch between the size passed to allocator in
> wilc_wlan_init, and the range of possible indexes used later:
> allocation
> size is missing a multiplication by sizeof(u32)
Nice catch.
> While at it, instead of simply multiplying the allocation size, do not
> keep
> dedicated dynamic allocation for vmm_table: define it as an array with
> the
> relevant size in wilc struct, which is already dynamically allocated
>
> Fixes: 40b717bfcefa ("wifi: wilc1000: fix DMA on stack objects")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
Looks good to me. But you'll change the alignment of the table, not sure
if that matters for some DMA controllers.
-michael
next prev parent reply other threads:[~2023-10-13 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 8:26 [PATCH] wifi: wilc1000: use vmm_table as array in wilc struct Alexis Lothoré
2023-10-13 9:24 ` Michael Walle [this message]
2023-10-16 6:59 ` Alexis Lothoré
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=f615b0895135489a2555d898afdcfbfa@kernel.org \
--to=mwalle@kernel.org \
--cc=ajay.kathat@microchip.com \
--cc=alexis.lothore@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=heiko.thiery@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.