netdev - Re: wfx: Memory corruption during high traffic with WFM200 on i.MX6Q platform

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 12 Sep 2022 18:15:53 +0200
From:   Jérôme Pouiller <jerome.pouiller@...abs.com>
To:     linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        Paweł Lenkow <pawel.lenkow@...lingroup.com>,
        Lech Perczak <lech.perczak@...lingroup.com>
Cc:     Kalle Valo <kvalo@...nel.org>,
        Krzysztof Drobiński 
        <krzysztof.drobinski@...lingroup.com>,
        Kirill Yatsenko <kirill.yatsenko@...lingroup.com>
Subject: Re: wfx: Memory corruption during high traffic with WFM200 on i.MX6Q platform

On Monday 12 September 2022 17:16:24 CEST Lech Perczak wrote:
> 
> Hello,
> 
> We're trying to get a WFM200S022XNN3 module working on a custom i.MX6Q board using SDIO interface, using upstream kernel. Our patches concern primarily the device tree for the board - and upstream firmware from linux-firmware repository.
> 
> During that, we stumbled upon a memory corruption issue, which appears when big traffic is passing through the device. Our adapter is running in AP mode. This can be reproduced with 100% rate using iperf3, by starting an AP interface on the device, and an iperf3 server. Then, the client station runs iperf3 with "iperf3 -c <hostname> -t 3600" command - so the AP is sending data for up to one hour, however - the kernel on our device crashes after around a few minutes of traffic, sometimes less than a minute.
> 
> The behaviour is the same on kernel v5.19.7, v5.19.2, and even with v6.0-rc5. Tests on v6.0-rc5 have shown most detailed stacktrace so far:
> 

Hello Lech,

It seems that something somewhere (Ms Exchange, I am looking at you) has
removed all the newlines of your mail :-/. Can you try to fix the problem?
I think that sending mails using base64 encoding would solve the issue.


[...]

-- 
Jérôme Pouiller