linux-kernel - Re: [PATCH V2] staging: fieldbus: anybus-s: force endiannes annotation

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]

Date:   Tue, 30 Apr 2019 10:22:42 -0400
From:   Sven Van Asbroeck <thesven73@...il.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Al Viro <viro@...iv.linux.org.uk>, devel@...verdev.osuosl.org,
        Nicholas Mc Guire <der.herr@...r.at>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Nicholas Mc Guire <hofrat@...dl.org>
Subject: Re: [PATCH V2] staging: fieldbus: anybus-s: force endiannes annotation

On Tue, Apr 30, 2019 at 10:03 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> Keep it bus-endian, as that's the "normal" way bus structures work (like
> PCI and USB for example), and that should be in a documented, and
> consistent, form, right?
>
> Then do the conversion when you access the field from within the kernel.

Ah ok, it's like a standard way of implementing a bus. Sounds good, I'll
spin a patch to conform to it. And while I'm at it, I'll rename fieldbus_type
because it can be confused with another fieldbus_type within the
fieldbus_dev core.