linux-kernel - bitmap namespace conflict

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

Message-ID: <ad0415db268750c033499e2b3bd079ca2c9f099d.camel@linux.intel.com>
Date:   Thu, 14 Jun 2018 17:46:36 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Shaohua Li <shli@...nel.org>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>, arnd@...db.de,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     linux-raid <linux-raid@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: bitmap namespace conflict

Hi!

There is a potential name space collision with bitmap API vs. MD bitmaps
(whatever it is).

Since I'm about to submit some extension to bitmap API, I would like as
a preparatory patch to rename all bitmap_* in drivers/md to md_bitmap_*
to avoid real conflict with my patch series [1], i.e. bitmap_free().

Opinions?
Better proposals?

[1]: https://patchwork.kernel.org/patch/10442771/
Almost RFC version

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