linux-kernel - Re: nl80211 wlcore regression in next

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <87r27irpjk.fsf@kamboji.qca.qualcomm.com>
Date:   Tue, 25 Jun 2019 12:18:39 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Tony Lindgren <tony@...mide.com>
Cc:     Johannes Berg <johannes@...solutions.net>,
        Eyal Reizer <eyalreizer@...il.com>,
        linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org
Subject: Re: nl80211 wlcore regression in next

Tony Lindgren <tony@...mide.com> writes:

> Hi,
>
> * Johannes Berg <johannes@...solutions.net> [190625 07:47]:
>> On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote:
>> > Hi,
>> > 
>> > Looks like at least drivers/net/wireless/ti wlcore driver has stopped
>> > working in Linux next with commit 901bb9891855 ("nl80211: require and
>> > validate vendor command policy"). Reverting the commit above makes it
>> > work again.
>> > 
>> > It fails with the warning below, any ideas what goes wrong?
>> 
>> Oops. For some reason, I neglected to check the vendor command usage
>> beyond hwsim.
>> 
>> The patch below should work?
>
> Yeah thanks that fixes the issue for me:
>
> Tested-by: Tony Lindgren <tony@...mide.com>

Acked-by: Kalle Valo <kvalo@...eaurora.org>

-- 
Kalle Valo