netdev - Re: [PATCH] can: proc: fix rcvlist_* header alignment on 64-bit system

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: <CAMZ6RqLdjYg49Sq3cp3dpseMMgTk+WoOvqXac=YuxdWas_xi7g@mail.gmail.com>
Date:   Sun, 25 Apr 2021 21:05:41 +0900
From:   Vincent MAILHOL <mailhol.vincent@...adoo.fr>
To:     Erik Flodin <erik@...din.me>
Cc:     Oliver Hartkopp <socketcan@...tkopp.net>,
        Marc Kleine-Budde <mkl@...gutronix.de>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        linux-can <linux-can@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH] can: proc: fix rcvlist_* header alignment on 64-bit system

On Sun. 25 Apr 2021 at 20:40, Erik Flodin <erik@...din.me> wrote:
>
> None of these versions are really grep friendly though. If that is
> needed, a third variant with two full strings can be used instead.
> Just let me know which one that's preferred.

Out of all the propositions, my favorite is the third variant
with two full strings.  It is optimal in terms of computing
time (not that this is a bottleneck...), it can be grepped and
the source code is easy to understand.