linux-kernel - Re: [GIT PULL] seccomp update for v5.18-rc1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CF7E8A5F-F80A-4FF2-8B0A-028C475DD045@chromium.org>
Date:   Mon, 21 Mar 2022 21:54:32 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
CC:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] seccomp update for v5.18-rc1



On March 21, 2022 7:45:51 PM PDT, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>On Mon, Mar 21, 2022 at 8:07 AM Kees Cook <keescook@...omium.org> wrote:
>>
>> Please pull this tiny seccomp update for v5.18-rc1.
>
>Well, that *really* didn't work at all.
>
>  In file included from samples/seccomp/dropper.c:29:
>  usr/include/linux/ptrace.h:50: warning: "PTRACE_GETREGSET" redefined
>     50 | #define PTRACE_GETREGSET        0x4204
>        |
>   In file included from samples/seccomp/dropper.c:24:
>  /usr/include/sys/ptrace.h:153: note: this is the location of the
>previous definition
>    153 | #define PTRACE_GETREGSET PTRACE_GETREGSET
>        |
>  [...]
>
>.. and a lot of similar warnings.

Oh, eww. Apologies! That didn't happen for my builders, but yeah, that code is super fragile anyway, so this just confirms my suspicion that the changes weren't useful. I'll drop it from my tree.

-- 
Kees Cook