netdev - Re: qla3xxx: Odd likely incorrect use of test

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: <20150514080116.GF8431@mwanda>
Date:	Thu, 14 May 2015 11:01:16 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Ron Mercer <ron.mercer@...gic.com>, linux-driver@...gic.com,
	netdev <netdev@...r.kernel.org>
Subject: Re: qla3xxx: Odd likely incorrect use of test_bit in qla3xxx.c

On Wed, May 13, 2015 at 10:34:51AM -0700, Joe Perches wrote:
> On Wed, 2015-05-13 at 16:19 +0300, Dan Carpenter wrote:
> > Good eye, Joe.
> > 
> > I wrote a Smatch check to find similar bugs.  Te rhey weren't any other
> > places which tried to do bitwise OR.  The bug that happens occasionally
> > is:
> > 
> > #define MY_FLAG BIT(1)
> > 
> > 	if (test_bit(MY_FLAG, &map)) {
> > 		...
> > 
> > It's not normally harmful if it's used consistently, but ath9k had
> > memory corruption because they do:
> > 
> > 	set_bit(BIT(6), &some_unsigned_long);
> > 
> > Anyway, I'll send patches for the bugs I found and push the Smatch
> > check. Thanks!
> 
> In case the patches you found weren't of this type,
> there are other possibly suspicious uses with & like:
> 
> drivers/usb/host/ehci-tegra.c:		set_bit((wIndex & 0xff) - 1, &ehci->suspended_ports);
>

That's puzzling, yes, but my instinct without looking at the context is
that it's probably valid.  I didn't look at that that one, but I looked
at a bunch of similar cases.

My test only looked at test_bit().  I'll update it to look at set_bit()
and clear_bit() as well.  It only complains about "test_bit(x | y, " and
"test_bit(x < y, ".

Btw, Smatch already has a check for when people do:

	set_bit(FOO_BIT, &flags);

	...

	if (flags & FOO_BIT) {

It looks uses the macro names, so if you open code it then it won't
catch the inconsistency, but mostly it works.

regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html