From: Kalle Valo <kvalo@kernel.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: arnd@arndb.de, tony@atomide.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org,
kernel@pyra-handheld.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH] wl1251: dynamically allocate memory used for DMA
Date: Fri, 6 May 2022 06:11:52 +0000 (UTC) [thread overview]
Message-ID: <165181750762.835.18351799442836112147.kvalo@kernel.org> (raw)
In-Reply-To: <1676021ae8b6d7aada0b1806fed99b1b8359bdc4.1651495112.git.hns@goldelico.com>
"H. Nikolaus Schaller" <hns@goldelico.com> wrote:
> With introduction of vmap'ed stacks, stack parameters can no
> longer be used for DMA and now leads to kernel panic.
>
> It happens at several places for the wl1251 (e.g. when
> accessed through SDIO) making it unuseable on e.g. the
> OpenPandora.
>
> We solve this by allocating temporary buffers or use wl1251_read32().
>
> Tested on v5.18-rc5 with OpenPandora.
>
> Fixes: a1c510d0adc6 ("ARM: implement support for vmap'ed stacks")
> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
Patch applied to wireless-next.git, thanks.
454744754cbf wl1251: dynamically allocate memory used for DMA
--
https://patchwork.kernel.org/project/linux-wireless/patch/1676021ae8b6d7aada0b1806fed99b1b8359bdc4.1651495112.git.hns@goldelico.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-05-06 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 12:38 [PATCH] wl1251: dynamically allocate memory used for DMA H. Nikolaus Schaller
2022-05-02 14:06 ` Arnd Bergmann
2022-05-02 14:47 ` H. Nikolaus Schaller
2022-05-02 15:04 ` Arnd Bergmann
2022-05-06 6:11 ` Kalle Valo [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=165181750762.835.18351799442836112147.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hns@goldelico.com \
--cc=kernel@pyra-handheld.com \
--cc=kuba@kernel.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tony@atomide.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).