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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 20 Oct 2009 19:59:04 -0400
From:	Jeff Moyer <>
To:	Zubin Dittia <>
Subject: Re: libaio asynchronous syscall io_getevents blocks on error

Zubin Dittia <> writes:

> But this does bring up the interesting question of how to know which
> of the I/Os I submitted had an error, and what the error was.  Does it

If io_submit returned N, then the N+1 iocb had an error.

> PS: It does seem a little strange that io_submit returns an error if
> the first IOCB is invalid but not when any of the other IOCBs are
> invalid (this appears to be the case, at least according to the man
> page).

It makes sense that it tells you how many it could successfully submit.
If it can't submit any, you get the error from the first I/O.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists