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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 21 Mar 2022 19:45:51 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Kees Cook <keescook@...omium.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] seccomp update for v5.18-rc1

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.

Yeah, that sample code is horrible, and mixes kernel headers with
regular user-space headers.

It did that before too, it just does it much more now, and simply
doesn't work. I'm sure this probably only happens on some distros, but
that's what you get when you play those kinds of broken games.

Pulled and immediately unpulled. That sample probably needs to just be removed.

                     Linus