linux-kernel - Re: byteorder: cpu_to_le32_array vs cpu_to_be32

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]

Date:   Mon, 21 Oct 2019 12:31:30 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Joe Perches <joe@...ches.com>
Cc:     Herbert Xu <herbert@...dor.apana.org.au>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: byteorder: cpu_to_le32_array vs cpu_to_be32_array function API
 differences

On Sun, Oct 20, 2019 at 12:02:52PM -0700, Joe Perches wrote:
> There's an argument inconsistency between these 4 functions
> in include/linux/byteorder/generic.h
> 
> It'd be more a consistent API with one form and not two.

This is done in order to:
 - avoid changing existing code
 - start a very this discussion to see what we can do if it's even needed to be done

So, do we have other places in the kernel which can utilize either of these?

-- 
With Best Regards,
Andy Shevchenko