netdev - Re: LTP recv/recvmsg tests failing on 3.17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+FuTSeyzMayJ6zR8KBpt_Wu-orCowMDtTOwXxp84-RobBZ1xA@mail.gmail.com>
Date:	Tue, 23 Sep 2014 12:24:57 -0400
From:	Willem de Bruijn <willemb@...gle.com>
To:	Chuck Ebbert <cebbert.lkml@...il.com>
Cc:	Network Development <netdev@...r.kernel.org>
Subject: Re: LTP recv/recvmsg tests failing on 3.17

> But I was also wondering why we return EAGAIN here for no data waiting,
> when we return EINVAL for the same case with a different type of data.
> There's no spec and it's not documented, so I guess the answer is "it's
> always been that way."

EAGAIN is the common response. I don't know why TCP urgent
data returns EINVAL. It is unusual enough that the relevant line
in tcp_recv_urg explicitly comments on it:

                return -EINVAL; /* Yes this is right ! */
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html