linux-kernel - Re: [PATCH v5] f2fs: fix zoned block device information initialization

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8c51d0d8-ae3d-418c-b6ac-5a164b40a8c5@oppo.com>
Date: Sun, 4 Feb 2024 11:35:45 +0800
From: Yongpeng Yang <yangyongpeng1@...o.com>
To: Wenjie Qi <qwjhust@...il.com>, jaegeuk@...nel.org, chao@...nel.org,
 linux-f2fs-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Cc: hustqwj@...t.edu.cn
Subject: Re: [PATCH v5] f2fs: fix zoned block device information
 initialization

Hi Wenjie,
"max_open_zones < sbi->max_open_zones" seems meaningless, this condition 
is false only if "max_open_zones == UINT_MAX"(rarely happen). Although 
it doesn't affect the correctness, I think less jmp instruction is better.

On 2/4/2024 11:10 AM, Wenjie Qi wrote:
> max_open_zones < sbi->max_open_zones