linux-kernel - [GIT PULL] siginfo fix for v4.16-rc5

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-next>] [day] [month] [year] [list]

Message-ID: <87woypy8zc.fsf@xmission.com>
Date:   Tue, 06 Mar 2018 01:11:03 -0600
From:   ebiederm@...ssion.com (Eric W. Biederman)
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     <linux-kernel@...r.kernel.org>,
        kernel test robot <shun.hao@...el.com>
Subject: [GIT PULL] siginfo fix for v4.16-rc5

Linus,

Please pull the siginfo-linus branch from the git tree:

   git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git siginfo-linus

   HEAD: f6a015498dcaee72f80283cb7873d88deb07129c signal/x86: Include the field offsets in the build time checks

The kbuild test robot found that I accidentally moved si_pkey when I was
cleaning up siginfo_t.  A short followed by an int with the int having 8
byte alignment.  Sheesh siginfo_t is a weird structure.

I have now corrected it and added build time checks that with a little
luck will catch any similar future mistakes.  The build time checks were
sufficient for me to verify the bug and to verify my fix.  So they are
at least useful this once.

Eric W. Biederman (2):
      signal: Correct the offset of si_pkey in struct siginfo
      signal/x86: Include the field offsets in the build time checks

 arch/x86/kernel/signal_compat.c    | 65 ++++++++++++++++++++++++++++++++++++++
 include/linux/compat.h             |  4 +--
 include/uapi/asm-generic/siginfo.h |  4 +--
 3 files changed, 69 insertions(+), 4 deletions(-)