From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933594Ab2C2R6u (ORCPT ); Thu, 29 Mar 2012 13:58:50 -0400 Received: from terminus.zytor.com ([198.137.202.10]:38587 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752096Ab2C2R6p (ORCPT ); Thu, 29 Mar 2012 13:58:45 -0400 Message-ID: <4F74A2C9.1000009@zytor.com> Date: Thu, 29 Mar 2012 10:58:33 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1 MIME-Version: 1.0 To: Kees Cook CC: "Ted Ts'o" , LKML Subject: Re: Correct way to include siginfo.h? References: <20120327172133.GB10142@thunk.org> <20120327173744.GD10142@thunk.org> In-Reply-To: X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/27/2012 11:01 AM, Kees Cook wrote: > > No, siginfo, IIUC, is defined to be SI_MAX_SIZE bytes. The union for > seccomp (on SIGSYS) just uses a long and 2 ints. It'd be nice for > there to be a stable way to get the kernel's siginfo instead of > glibc's. > Make it safe for the kernel to export and make glibc use the kernel's version, just like everything else... -hpa