From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933187AbXCHTeL (ORCPT ); Thu, 8 Mar 2007 14:34:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933188AbXCHTeK (ORCPT ); Thu, 8 Mar 2007 14:34:10 -0500 Received: from mtaout5.012.net.il ([84.95.2.13]:29219 "EHLO mtaout5.012.net.il" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933187AbXCHTeI (ORCPT ); Thu, 8 Mar 2007 14:34:08 -0500 Date: Thu, 08 Mar 2007 21:34:00 +0200 From: Avi Kivity Subject: Re: [patch 2/5] signalfd v2 - signalfd core ... In-reply-to: To: Davide Libenzi Cc: Linus Torvalds , "David M. Lloyd" , Linux Kernel Mailing List , Andrew Morton Message-id: <45F06528.7040506@argo.co.il> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.12 (firebolt.argo.co.il [0.0.0.0]); Thu, 08 Mar 2007 21:34:00 +0200 (IST) References: <1173364264.6891.3.camel@localhost> User-Agent: Thunderbird 1.5.0.9 (X11/20070212) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Davide Libenzi wrote: > So, to cut it short, I can do the pseudo-siginfo read(2), but I don't > like it too much (little, actually). The siginfo, as bad as it is, is a > standard used in many POSIX APIs (hence even in kernel), and IMO if we > want to send that back, a struct siginfo should be. > You can send the data in the 32/64 neutral format, and have glibc convert it to a siginfo, and everybody's happy. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.