linux-kernel - Re: [PATCH] sched: Use kmem_cache_zalloc() instead of kmem_cache_alloc() with flag GFP

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: <20200212101108.GE14914@hirez.programming.kicks-ass.net>
Date:   Wed, 12 Feb 2020 11:11:08 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Yi Wang <wang.yi59@....com.cn>
Cc:     mingo@...hat.com, juri.lelli@...hat.com,
        vincent.guittot@...aro.org, dietmar.eggemann@....com,
        rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
        linux-kernel@...r.kernel.org, xue.zhihong@....com.cn,
        wang.liang82@....com.cn, Huang Zijiang <huang.zijiang@....com.cn>
Subject: Re: [PATCH] sched: Use kmem_cache_zalloc() instead of
 kmem_cache_alloc() with flag GFP_ZERO.

On Wed, Feb 12, 2020 at 05:54:21PM +0800, Yi Wang wrote:
> From: Huang Zijiang <huang.zijiang@....com.cn>
> 
>  Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc
>  with flag GFP_ZERO since kzalloc sets allocated memory
>  to zero.
> 
>  Change in v2:
>       add indation

Why? Isn't this more or less a whitespace change?