Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756980AbZAMWsV (ORCPT ); Tue, 13 Jan 2009 17:48:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752650AbZAMWsK (ORCPT ); Tue, 13 Jan 2009 17:48:10 -0500 Received: from mx1.redhat.com ([66.187.233.31]:59884 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752265AbZAMWsI (ORCPT ); Tue, 13 Jan 2009 17:48:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: mtk.manpages@gmail.com X-Fcc: ~/Mail/linus Cc: "kernel list" , "Ulrich Drepper" , "Vegard Nossum" , "linux-man@vger.kernel.org" Subject: Re: waitid() return value strangeness when infop is NULL In-Reply-To: Michael Kerrisk's message of Wednesday, 14 January 2009 11:38:18 +1300 References: X-Shopping-List: (1) Blunt companions (2) Deoxyribonucleic trenchant chains (3) Irritating reinforcements Message-Id: <20090113224759.7DFB7FC3DD@magilla.sf.frob.com> Date: Tue, 13 Jan 2009 14:47:59 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 467 Lines: 14 > a) Is it intentional to support the infop==NULL case for waitid() -- > rather than simply giving an error return? No. It's just an artifact of the internals shared with wait4/waitpid. Patch to follow. Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/