All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, balbir_soni@yahoo.com, jholly@cup.hp.com,
	plars@austin.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: readv() return and errno
Date: Tue, 26 Mar 2002 21:15:44 GMT	[thread overview]
Message-ID: <UTC200203262115.VAA429771.aeb@cwi.nl> (raw)

    From jholly@cup.hp.com Tue Mar 26 18:13:40 2002

    Doesn't seem confusing at all.

    RETURN VALUE
           On  success  readv  returns  the number of bytes read.  On
           success writev returns the number of  bytes  written.   On
           error, -1 is returned, and errno is set appropriately.

    ERRORS
           EINVAL An  invalid  argument was given. For instance count
                  might be greater than MAX_IOVEC, or zero.  fd could
                  also  be  attached to an object  which  is  unsuit-
                  able  for  reading  (for  readv)  or  writing  (for
                  writev).

    I don't see much in the way of waffle words. If count is greater than
    MAX_IOVEC or zero you get EINVAL.

Yes, without hesitation you choose the wrong interpretation.
That is why I explained in so much detail what the right
interpretation is. Since you perhaps still do not understand,
let me reiterate:

The above ERRORS section says: In case this call returns EINVAL
one of the possible reasons is that an invalid argument was given.
There do exist Unix-like systems (not necessarily Linux) that
consider a zero count invalid.

Andries

             reply	other threads:[~2002-03-26 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 21:15 Andries.Brouwer [this message]
2002-03-26 23:40 ` readv() return and errno Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-03-26 21:37 Andries.Brouwer
2002-03-26 23:38 ` Alan Cox
2002-03-26 17:13 Jim Hollenback
2002-03-26 18:06 ` Alan Cox
2002-03-26 16:19 Andries.Brouwer
2002-03-26 17:01 ` Balbir Singh
2002-03-15 23:15 Balbir Singh
2002-03-15 21:54 Jim Hollenback
2002-03-19 13:27 ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=UTC200203262115.VAA429771.aeb@cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=balbir_soni@yahoo.com \
    --cc=jholly@cup.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plars@austin.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.