X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=omlp
	RwT0uuez3vdulxzl+pEWBsWRWrUKg0Q3n3jRk7WCQuLvdC28jMfsWyCk/qvTXaO2
	t7rvoKXNQ+CgUX7PSrUM61XrTZaTYLlm/xlMolgGKaHfzwCJa+JgY+5jgpqweoLS
	XR20dx6AYHgyF4WMsiWOLkMmaODnhZphv1r1bZ8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; s=default; bh=Rmzj6Qbxtl
	JaBP1DFIVGNTmDqMU=; b=HbJ8aMqUCBT+30+YJLFCGnE3ZJB4MZqutslxu5ria5
	70cJEL+LQWpACr0ilurWu3LR3MRSxhq9zcHAIq5cwfNm7tgA6GZ/avBPJOLvJ4EU
	PXj+DzzMXEZ/RZxp9I6kqCBlBJH8ujKzi6yM9j5lUY+60VS1/6jy7arpekZ6G0ja
	s=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=
X-HELO: mx1.redhat.com
Subject: Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard
To: cygwin AT cygwin DOT com
References: <0873126E9D101A4A983DE738F4346DBC9114A8F3 AT NAWESPSCXM03V DOT nadsuswe DOT nads DOT navy DOT mil> <20190424164358 DOT GG30041 AT calimero DOT vinschen DOT de> <4e01e86d-83c9-5855-c4a5-29f5375dc2dc AT cs DOT umass DOT edu> <a1cb4f3e-ae07-26c2-aa7f-695f2a178961 AT t-online DOT de> <f73771ca-780c-cde3-2edc-08bb60b1c261 AT redhat DOT com> <3a646fc6-82cb-1980-cc85-75cd4db6f3a0 AT SystematicSw DOT ab DOT ca>
From: Eric Blake <eblake AT redhat DOT com>
Openpgp: preference=signencrypt
Message-ID: <f3ff4eb7-0490-3b53-e45d-9145e7a932c3@redhat.com>
Date: Thu, 25 Apr 2019 10:48:18 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <3a646fc6-82cb-1980-cc85-75cd4db6f3a0@SystematicSw.ab.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FXtZydyqnH6rP7inUjDxfQnn7uh3jzZej"
X-IsSubscribed: yes

--FXtZydyqnH6rP7inUjDxfQnn7uh3jzZej
Content-Type: multipart/mixed; boundary="o8OKuJYABuIRpkOcbmdRZlmCbFheGLMhb";
 protected-headers="v1"
From: Eric Blake <eblake AT redhat DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <f3ff4eb7-0490-3b53-e45d-9145e7a932c3 AT redhat DOT com>
Subject: Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per
 the POSIX standard
References: <0873126E9D101A4A983DE738F4346DBC9114A8F3 AT NAWESPSCXM03V DOT nadsuswe DOT nads DOT navy DOT mil>
 <20190424164358 DOT GG30041 AT calimero DOT vinschen DOT de>
 <4e01e86d-83c9-5855-c4a5-29f5375dc2dc AT cs DOT umass DOT edu>
 <a1cb4f3e-ae07-26c2-aa7f-695f2a178961 AT t-online DOT de>
 <f73771ca-780c-cde3-2edc-08bb60b1c261 AT redhat DOT com>
 <3a646fc6-82cb-1980-cc85-75cd4db6f3a0 AT SystematicSw DOT ab DOT ca>
In-Reply-To: <3a646fc6-82cb-1980-cc85-75cd4db6f3a0 AT SystematicSw DOT ab DOT ca>


--o8OKuJYABuIRpkOcbmdRZlmCbFheGLMhb
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 4/25/19 10:28 AM, Brian Inglis wrote:

>> - add a define for MSG_EOR to a non-zero value that is bitwise distinct
>> from other required MSG_ values
>> - return EOPNOTSUPP on attempts to use the flag in
>> send()/sendmsg()/sendto() (POSIX permits that failure for protocols that
>> don't support it - and none of Cygwin's protocols support it)

>>
>> although I personally thought POSIX was clear enough that MSG_EOR is
>> required to be defined, even if only so that it can trigger send()
>> errors showing that it is unsupported.
>=20
> Would it be allowed and valid to #define MSG_EOR 0 to simplify lack of su=
pport?

No, because that implies that EVERY send() call is requesting MSG_EOR
and that it never fails.  Defining it to a distinct non-zero value makes
it possible to report EOPNOTSUPP.

--=20
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


--o8OKuJYABuIRpkOcbmdRZlmCbFheGLMhb--

--FXtZydyqnH6rP7inUjDxfQnn7uh3jzZej
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEccLMIrHEYCkn0vOqp6FrSiUnQ2oFAlzB1sIACgkQp6FrSiUn
Q2o1fAf+JPvbGqWNF6NaPC6+MLUsG5E/CfQj1ZGdkeXNhH5C9z4PWMp5R5oCB2fD
uZVjjrPCCWrasEexmT/dtb4LpcQwZ+eDFZIoVhvoQ4jnkajtNpEp2rCQaQXA6SVQ
0d+rrWS9n4Q5OWMz1vrYqlgGEXJzm/4WtTsHFiFi3I0rwGP2KltQgst4CJ7e8aYW
FkfQXXnNSQuoTAn3eppXxHvQuIFxX27BRLsK+IvmH81NNFmey9yf3DBMVcHcGH7o
HgbncIIOZD8HCY9dNr22TT5k9E933CEXijbG7XYEP3r7VstSjxp0BHXKQSRVLwlw
SV7BZUicQRQV3MyEwvdJRYy+Mjhk9w==
=AK4g
-----END PGP SIGNATURE-----

--FXtZydyqnH6rP7inUjDxfQnn7uh3jzZej--