linux-kernel - Re: [PATCH v2 01/10] usb: host: ehci-sched: refactor scan

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: <CAGG-pURE=zkkz9tsN4cs0v0Xjoh-=j+PGcJLydYpH88g5e+Wqw@mail.gmail.com>
Date:	Sun, 13 Dec 2015 13:35:09 -0300
From:	"Geyslan G. Bem" <geyslan@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Peter Senna Tschudin <peter.senna@...il.com>,
	linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 01/10] usb: host: ehci-sched: refactor scan_isoc function

2015-12-13 12:29 GMT-03:00 Alan Stern <stern@...land.harvard.edu>:
> On Sun, 13 Dec 2015, Geyslan G. Bem wrote:
>
>> This patch removes an infinite 'for' loop and makes use of the already
>> existing 'restart' tag instead, reducing one leading tab.
>>
>> It also puts the easier evaluation (live variable) to be the first in
>> two conditionals.
>>
>>   if (live && frame == now_frame) { ...
>>
>>   if (live && ((frame == now_frame) || ...
>
> You should never do this.  The first test in a conditional should be
> the one that is most likely to cause the expression to fail.  In this
> case, live is almost always true whereas frame == now_frame is true
> only some percentage of the time.  Therefore the frame == now_frame
> test should come first.
I see.
Doing v3 and undoing the reordering.

>
> Alan Stern
>



-- 
Regards,

Geyslan G. Bem
hackingbits.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/