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] [day] [month] [year] [list]
Message-ID: <875yuuwka6.fsf@codeaurora.org>
Date:   Tue, 21 Sep 2021 08:49:05 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Martin Fuzzey <martin.fuzzey@...wbird.group>
Cc:     linux-wireless@...r.kernel.org,
        Amitkumar Karwar <amitkarwar@...il.com>,
        Siva Rebbagondla <siva8118@...il.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Prameela Rani Garnepudi <prameela.j04cs@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] rsi: fix startup and P2P mode

Martin Fuzzey <martin.fuzzey@...wbird.group> writes:

> This series fixes an occasional startup failure when BT
> coexistence is enabled and makes P2P mode work
> (the two are unrelated but sending as a series since the same files
> are modified).
>
> Tested on RS9116 in P2P client mode against an Android phone (S8, Android 9)
>
> For an unknown reason GO mode does not work against the phone but it
> does work against a second RS9116 device.
> In this case Android does not send a response to the 3rd WPA handshake
> packet. It is difficult to debug this without the phone wpa_supplicant
> logs which I don't have.
>
> Regression tested OK for STA and AP modes.
>
> V2:
>   * rebase against wireless-drivers-next
>   * add cc: stable to patches 2 & 3
>
> Martin Fuzzey (3):
>   rsi: fix occasional initialisation failure with BT coex
>   rsi: fix key enabled check causing unwanted encryption for vap_id > 0
>   rsi: fix rate mask set leading to P2P failure

BTW thanks for the outstanding cover letter and commit logs in the
patches, it was so easy for me to understand the background and the
level of testing these patches have had. If everyone would write their
patches like this my job would be a lot easier :)

I'm going to use this patchset as an example in the submittingpatches
wiki page.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ