netdev - Re: [PATCH -next] selftests/seccomp: Use bitwise instead of arithmetic operator for flags

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]

Message-Id: <159960731879.1678444.6814133998182138035.b4-ty@chromium.org>
Date:   Tue,  8 Sep 2020 16:22:12 -0700
From:   Kees Cook <keescook@...omium.org>
To:     kafai@...com, songliubraving@...com,
        linux-kselftest@...r.kernel.org, luto@...capital.net,
        wad@...omium.org, daniel@...earbox.net, john.fastabend@...il.com,
        kpsingh@...omium.org, shuah@...nel.org, netdev@...r.kernel.org,
        Zou Wei <zou_wei@...wei.com>, yhs@...com, andriin@...com,
        bpf@...r.kernel.org, ast@...nel.org, linux-kernel@...r.kernel.org
Cc:     Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH -next] selftests/seccomp: Use bitwise instead of arithmetic operator for flags

On Wed, 15 Apr 2020 12:15:01 +0800, Zou Wei wrote:
> This silences the following coccinelle warning:
> 
> "WARNING: sum of probable bitmasks, consider |"
> 
> tools/testing/selftests/seccomp/seccomp_bpf.c:3131:17-18: WARNING: sum of probable bitmasks, consider |
> tools/testing/selftests/seccomp/seccomp_bpf.c:3133:18-19: WARNING: sum of probable bitmasks, consider |
> tools/testing/selftests/seccomp/seccomp_bpf.c:3134:18-19: WARNING: sum of probable bitmasks, consider |
> tools/testing/selftests/seccomp/seccomp_bpf.c:3135:18-19: WARNING: sum of probable bitmasks, consider |

Applied, thanks!

[1/1] selftests/seccomp: Use bitwise instead of arithmetic operator for flags
      https://git.kernel.org/kees/c/76993fe3c1e4

Sorry for the massive delay on this one! I lost this email in my inbox. :)

-- 
Kees Cook