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]
Date:   Fri, 4 Mar 2022 14:32:57 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Jiapeng Chong <jiapeng.chong@...ux.alibaba.com>,
        David Miller <davem@...emloft.net>
Cc:     davem@...emloft.net, kuba@...nel.org, gustavoars@...nel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        Abaci Robot <abaci@...ux.alibaba.com>
Subject: Re: [PATCH v2] net: ethernet: sun: Remove redundant code

On Fri, Mar 04, 2022 at 04:36:53PM +0800, Jiapeng Chong wrote:
> Since the starting value in the for loop is greater than or equal to 1,
> the restriction is CAS_FLAG_REG_PLUS is in the file cassini.h is
> defined as 0x1 by macro, and the for loop and if condition is not
> satisfied, so the code here is redundant.

This still does not make much sense. Too late, David has merged it.

Taking a deeper look, we see:

https://elixir.bootlin.com/linux/v5.17-rc6/source/drivers/net/ethernet/sun/cassini.h#L2542
#define N_RX_COMP_RINGS               0x1 /* for mult. PCI interrupts */

So what the bot is reporting:

> drivers/net/ethernet/sun/cassini.c:3513 cas_start_dma() warn: we never
> enter this loop.
> 
> drivers/net/ethernet/sun/cassini.c:1239 cas_init_rx_dma() warn: we never
> enter this loop.
> 
> drivers/net/ethernet/sun/cassini.c:1247 cas_init_rx_dma() warn: we never
> enter this loop.
> 
> -	if (cp->cas_flags & CAS_FLAG_REG_PLUS) {
> -		for (i = 1; i < N_RX_COMP_RINGS; i++)
> -			readl(cp->regs + REG_PLUS_INTRN_STATUS_ALIAS(i));

has nothing to do with CAS_FLAG_REG_PLUS, which you say in your commit
message. It has to do with N_RX_COMP_RINGS. 

So you have 'fixed' a bots warning by removing code which cannot be
used. But is this the correct fix? Or has the bot actually found a
bug? Don't you think somebody wrote this code expecting it to be used?
Or do you think people write extra code which will never be used for
fun?

Looking at the git history, this code was actually written by DaveM.

Dave, this very old code, do you still remember this hardware? Bug or
dead code?

     Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ