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: Michael van Elst <mlelstv%serpens.de@localhost>
Subject: Re: kern/54435: reading TCP urgent data with MSG_OOB doesn't clear
 poll(2) status
Date: Mon, 5 Aug 2019 10:21:10 +0300

 On Mon, Aug 05, 2019 at 04:15:01 +0000, Michael van Elst wrote:
 
 >  And I tell you that this is expected behaviour. It's not a second
 >  stream that you can just read independently (poll/select, then
 >  read) and a program that acts normally on POLLIN wouldn't even see
 >  that.
 
 I asked for a reference (a book, an old mail, personal communication
 from someone who implemented it, something) and you just keep
 restating the same thing without any further argument than "b/c I say
 so".  You say it's expected, I say it doesn't make sense to me.
 
   read           - returns "a"
   read(MSG_OOB)  - returns "b"
   poll           - ?
 
 Are you saying it's illegal to call poll there?
 
 Are you saying it's correct for poll to return POLLPRI there when
 there's no MSG_OOB data to read?
 
 -uwe