From owner-freebsd-standards@FreeBSD.ORG Sun Jan 16 22:08:38 2011 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDCBC106564A for ; Sun, 16 Jan 2011 22:08:36 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3EB678FC08 for ; Sun, 16 Jan 2011 22:08:35 +0000 (UTC) Received: by wyf19 with SMTP id 19so4663285wyf.13 for ; Sun, 16 Jan 2011 14:08:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:cc:content-type; bh=BH1gt2+Dz/G+WygClnKlVV/T469eNDmApmADYJhMZ4Q=; b=O7GUqxpdKdKLpadb4ab8kDoQatCAEgmEc1o1Zee9LRzsJTAHxCpNbRwfWfz196ikvc PMipuhBBeYvYh2oTX5tepU2BZLItW8HH/lFz1NEJcfywEJEL2tfM+BDXH2f+gY3fap8O GIgvRlTVLJqmJIdIaR4LMQEMpWhmaQoq5TAxs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; b=xtxMPAmY0SF1VZ04oGnfZY4LHFyiys6OvKSb6zLJCJzmoH/DAoc+ZTFHs7rW+N+86y fhB2zSGU1CtUKUDrGUeFEetoCszSyX/A6vVWmWGHNTYRGy6Fr/BSLGn9nNg6BBRTCfSN MUpe18CTuhai8eLqoFMHTlVrbJGb2H9gvbVao= MIME-Version: 1.0 Received: by 10.216.78.146 with SMTP id g18mr2738793wee.1.1295214600852; Sun, 16 Jan 2011 13:50:00 -0800 (PST) Sender: yanegomi@gmail.com Received: by 10.216.254.226 with HTTP; Sun, 16 Jan 2011 13:50:00 -0800 (PST) Date: Sun, 16 Jan 2011 13:50:00 -0800 X-Google-Sender-Auth: daXWmE-JcrqY8AWWKplZsY6PDNU Message-ID: From: Garrett Cooper To: bug-followup@FreeBSD.org, rmh@aybabtu.com Content-Type: text/plain; charset=ISO-8859-1 Cc: standards@freebsd.org Subject: Re: standards/92362: [headers] [patch] Missing SIGPOLL in kernel headers X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2011 22:08:39 -0000 The OP's claim is wrong. SIGIO is a signal that can be discarded, whereas SIGPOLL by definition terminates processes. From SUSv7 (pardon the poor formatting): The following signals shall be supported on all implementations (default actions are explained below the table): Signal Default Action Description SIGPOLL T Pollable event. T Abnormal termination of the process. The process is terminated with all the consequences of _exit() except that the status made available to wait() and waitpid() indicates abnormal termination by the specified signal. From signal(3) (pardon the poor formatting): 23 SIGIO discard signal I/O is possible on a descriptor (see fcntl(2)) SIGPOLL is actually somewhere between SIGIO and SIGIOT (SIBABRT), but there isn't a 1:1 mapping for the signal definition. This is also XSI Stream specific (which is not [fully] implemented in [Free]BSD). SIGIO is also used by fcntl(2) to denote when I/O is available, but this connotation is not noted in SUSv7 either. This item should probably be closed as WONTFIX as we don't implement SIGPOLL in its proper form. Thanks, -Garrett PS FWIW GNU/Linux needs to be educated on the fact that SIGIO is a discardable signal on other platforms and not an alias for SIGPOLL on BSD (especially when they use it as an alias but don't document the requirement >:(...), because a quick look at some glibc and Linux headers shows that they are using them as a 1:1 mapping (I am using Fedora 13 as a reference).