mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: John Myers <jgmyers@netscape.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-aio@kvack.org" <linux-aio@kvack.org>
Subject: Re: [PATCH 2.5.71-mm1] aio process hang on EINVAL
Date: Thu, 19 Jun 2003 01:41:30 +0100	[thread overview]
Message-ID: <20030619004130.GP7895@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3EF104D7.5050905@netscape.com>

On Wed, Jun 18, 2003 at 05:33:27PM -0700, John Myers wrote:
> The kernel would have to be substantially more complex to report all 
> errors that could possibly be detected during queuing.  The kernel could 
> even detect success during queuing if it really tried.

	The slippery slope isn't important.  POSIX specifies EAGAIN
(you concede that), EBADF, and EINVAL against nbytes|offset|reqprio.
The kernel does these checks already (where applicable).
	Anyway, a caller of io_submit() already has to handle errors.
Just like a short read, you always have to be wary of them.

Joel

-- 

"Glory is fleeting, but obscurity is forever."  
         - Napoleon Bonaparte

			http://www.jlbec.org/
			jlbec@evilplan.org

  reply	other threads:[~2003-06-19  0:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17  0:43 Daniel McNeil
2003-06-17  1:33 ` John Myers
2003-06-17  3:24   ` Suparna Bhattacharya
2003-06-17 18:31     ` John Myers
2003-06-17 21:06     ` Daniel McNeil
2003-06-18  0:03       ` John Myers
2003-06-18  0:15         ` Joel Becker
2003-06-18  0:25           ` John Myers
2003-06-18  0:42             ` Joel Becker
2003-06-19  0:33               ` John Myers
2003-06-19  0:41                 ` Joel Becker [this message]
2003-06-19  0:58                   ` John Myers
2003-06-19  1:48                 ` Scot McKinley
2003-06-19 20:54                   ` John Myers
2003-06-19 22:42                     ` Scot McKinley
2003-06-18  5:11         ` Scot McKinley

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=20030619004130.GP7895@parcelfarce.linux.theplanet.co.uk \
    --to=jlbec@evilplan.org \
    --cc=jgmyers@netscape.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®