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  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]
Date:   Mon, 17 Aug 2020 16:27:01 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     davem@...emloft.net, kuba@...nel.org, linux-kernel@...r.kernel.org,
        Benjamin Reed <breed@...rs.sourceforge.net>,
        Javier Achirica <achirica@...rs.sourceforge.net>,
        Jean Tourrilhes <jt@....hp.com>,
        Fabrice Bellet <fabrice@...let.info>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        Ondrej Zary <linux@...nbow-software.org>
Subject: Re: [PATCH 12/30] net: wireless: cisco: airo: Fix a myriad of coding style issues

Lee Jones <lee.jones@...aro.org> writes:

> On Fri, 14 Aug 2020, Kalle Valo wrote:
>
>> Lee Jones <lee.jones@...aro.org> writes:
>> 
>> >  - Ensure spaces appear after {for, if, while, etc}
>> >  - Ensure spaces to not appear after '('
>> >  - Ensure spaces to not appear before ')'
>> >  - Ensure spaces appear between ')' and '{'
>> >  - Ensure spaces appear after ','
>> >  - Ensure spaces do not appear before ','
>> >  - Ensure spaces appear either side of '='
>> >  - Ensure '{'s which open functions are on a new line
>> >  - Remove trailing whitespace
>> >
>> > There are still a whole host of issues with this file, but this
>> > patch certainly breaks the back of them.
>> >
>> > Cc: Kalle Valo <kvalo@...eaurora.org>
>> > Cc: "David S. Miller" <davem@...emloft.net>
>> > Cc: Jakub Kicinski <kuba@...nel.org>
>> > Cc: Benjamin Reed <breed@...rs.sourceforge.net>
>> > Cc: Javier Achirica <achirica@...rs.sourceforge.net>
>> > Cc: Jean Tourrilhes <jt@....hp.com>
>> > Cc: Fabrice Bellet <fabrice@...let.info>
>> > Cc: linux-wireless@...r.kernel.org
>> > Cc: netdev@...r.kernel.org
>> > Signed-off-by: Lee Jones <lee.jones@...aro.org>
>> > ---
>> >  drivers/net/wireless/cisco/airo.c | 897 ++++++++++++++++--------------
>> >  1 file changed, 467 insertions(+), 430 deletions(-)
>> 
>> This is a driver for ancient hardware, I'm not sure if it's worth trying
>> to fix any style issues. Is anyone even using it? Should we instead just
>> remove the driver?
>
> Sounds like a reasonable solution to me.
>
> I'm also happy to do it, if there are no objections.
>
> As it stands, it's polluting the code-base and the build-log, so
> something should be done.

I tried to find some comments about the driver and here's one successful
report from 2013:

https://martybugs.net/wireless/aironet4800.cgi

And here's one commit from 2015 where Ondrej (CCed) was also testing the
driver:

----------------------------------------------------------------------
commit dae0412d0caa4948da07fe4ad91352b5b61a70ec
Author:     Ondrej Zary <linux@...nbow-software.org>
AuthorDate: Fri Oct 16 21:04:14 2015 +0200
Commit:     Kalle Valo <kvalo@...eaurora.org>
CommitDate: Wed Oct 28 20:54:39 2015 +0200

    airo: fix scan after SIOCSIWAP (airo_set_wap)
    
    SIOCSIWAP (airo_set_wap) affects scan: only the AP specified by
    SIOCSIWAP is present in scan results.
    
    This makes NetworkManager work for the first time but then unable to
    find any other APs.
    
    Clear APList before starting scan and set it back after scan completes
    to work-around the problem.
    
    To avoid losing packets during scan, modify disable_MAC() to omit
    netif_carrier_off() call when lock == 2.
    
    Signed-off-by: Ondrej Zary <linux@...nbow-software.org>
    Signed-off-by: Kalle Valo <kvalo@...eaurora.org>
----------------------------------------------------------------------

I was surprised to see that someone was using this driver in 2015, so
I'm not sure anymore what to do. Of course we could still just remove it
and later revert if someone steps up and claims the driver is still
usable. Hmm. Does anyone any users of this driver?

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

Powered by blists - more mailing lists