Re: kern/54435: reading TCP urgent data with MSG_OOB doesn't clear poll(2) status

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

The following reply was made to PR kern/54435; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: Robert Elz <kre%munnari.OZ.AU@localhost>
Subject: Re: kern/54435: reading TCP urgent data with MSG_OOB doesn't clear
 poll(2) status
Date: Thu, 8 Aug 2019 01:51:52 +0300

 On Mon, Aug 05, 2019 at 14:10:01 +0000, Robert Elz wrote:
 
 >  Certainly not for TCP, where SO_OOBINLINE should always be used really.
 
 There's even an RFC for that - https://tools.ietf.org/html/rfc6093
 
 But I think TCP urgent data is the only "out-of-band" thing we have,
 so it has to be the guinea pig for this out of necessity.
 
 And since we do provide recv(MSG_OOB) we might as well provide
 non-buggy poll to go with it.
 
 -uwe