Re: [ECOS] Misguided error code in net code?

[Jonathan Larmour <jlarmour at redhat dot com>]

Gary Thomas wrote:
> 
> On 19-Jul-2001 Trenton D. Adams wrote:
> > I just ran a test sending a big string from eCos over the network.  My
> > one end terminated prematurely because I forgot to put in a loop because
> > my buffer is only 8K.  Anyhow, on the eCos end I got an error of 22
> > (EINVAL) from send.  I could be wrong, but this seems like a pretty
> > weird error when the other end drops the connection.  I would have
> > expected ECONNRESET.
> >
> 
> I disagree - your request sounds pretty "invalid" to me.
> 
> Honestly, most of this stuff (like what errors get returned when) come
> from the standard BSD stack we're using - code that's been out there for
> twenty years.  (The numeric values may be different, but the codes the same)

While that's true, the world moves on, and the upcoming update to POSIX
1003.1 now says it should return EPIPE (or possibly ECONNRESET). After a
brief look, it's probably returning EINVAL at line 228 of
sys/netinet/tcp_usrreq.c but I don't know for sure. Even so, I couldn't be
sure that changing that to ECONNRESET is appropriate because I wouldn't
know what other circumstances could cause this to happen. Trenton, if
you're sufficiently bothered, feel free to investigate.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/