From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00,
 URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2
X-Original-To: kgio-public@bogomips.org
Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net
 (Postfix) with ESMTP id CD98F633858; Fri, 13 Feb 2015 20:33:37 +0000 (UTC)
Date: Fri, 13 Feb 2015 20:33:37 +0000
From: Eric Wong <e@80x24.org>
To: kgio-public@bogomips.org
Subject: Re: [RFC] use MSG_NOSIGNAL under Linux 2.2+
Message-ID: <20150213203337.GA21325@dcvr.yhbt.net>
References: <20150213201206.GA20113@dcvr.yhbt.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150213201206.GA20113@dcvr.yhbt.net>
List-Id: <kgio-public@bogomips.org>

Eric Wong <e@80x24.org> wrote:
>  ext/kgio/read.c  | 10 ++++++++--
>  ext/kgio/write.c |  2 +-

And further inspection of the Linux kernel reveals MSG_NOSIGNAL only
affects writers, not readers, so the read.c changes are no-ops.