linux-kernel - Re: [PATCH] vsprintf: Use non-atomic bitmap API when applicable

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: <YaSkSnLws3zSDhJT@alley>
Date:   Mon, 29 Nov 2021 10:58:34 +0100
From:   Petr Mladek <pmladek@...e.com>
To:     Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc:     rostedt@...dmis.org, senozhatsky@...omium.org,
        andriy.shevchenko@...ux.intel.com, linux@...musvillemoes.dk,
        linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] vsprintf: Use non-atomic bitmap API when applicable

On Sat 2021-11-27 15:27:35, Christophe JAILLET wrote:
> The 'set' bitmap is local to this function. No concurrent access to it is
> possible.
> So prefer the non-atomic '__[set|clear]_bit()' function to save a few
> cycles.
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>

Makes sense:

Reviewed-by: Petr Mladek <pmladek@...e.com>

Best Regards,
Petr