linux-kernel - bitmap API consistency

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-next>] [day] [month] [year] [list]

Message-ID: <1495627881.6967.99.camel@linux.intel.com>
Date:   Wed, 24 May 2017 15:11:21 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Rasmus Villemoes <linux@...musvillemoes.dk>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: bitmap API consistency

Hi!

Surprisingly discovered today that bitmap API is not consistent in some
cases (at least one I found recently).

bitmap_fill() sets area of bits in a bitmap.
bitmap_zero() clears them.

However, if _fill() does something sane, _zero() clears _all_ bits up to
word size (long).

I think it should be fixed to be consistent with _fill() variant.

Thoughts?

-- 
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy