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 16:34:04 -0700
From:	Zubin Dittia <>
To:	Jeff Moyer <>
Subject: Re: libaio asynchronous syscall io_getevents blocks on error

On Tue, Oct 20, 2009 at 3:25 PM, Jeff Moyer <> wrote:
> Zubin Dittia <> writes:
>> I'm writing a program that uses the kernel's io_submit/io_getevents
>> system calls.  What I would like to be able to do is submit N
>> operations for i/o on different files, and then call io_getevents with
>> min_nr = nr = N and a timeout of NULL, so that I can block until all N
>> operations have completed.  This works great, except when one of the
>> operations has an error (eg., if one of the descriptors is invalid).
>> In this case, the call to io_getevents appears to block indefinitely.
>> Shouldn't an error on one of the submitted operations count as a
>> completion event for that operation, so I can check the error code
>> when the call returns?  Any help would be appreciated.
> Did you check the return value of io_submit?
> Cheers,
> Jeff

Duh.  I was just checking to see if it returned a negative error, but
not checking to see if it accepted fewer than all the I/Os I

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
mean I have to call io_submit once for each I/O operation; if so, then
why does io_submit take an array argument at all?

Thanks for your help,

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
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