linux-kernel - Re: libaio asynchronous syscall io

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 20 Oct 2009 17:10:55 -0700
From:	Zubin Dittia <zubin@...tri.com>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: libaio asynchronous syscall io_getevents blocks on error

Thanks, Jeff, this makes sense.  In order to get error codes for all
I/Os that are being submitted, I'll have to loop calling io_submit on
successively smaller portions of the initial array of requests, each
time trimming off the ones that have been successfully submitted.
-Zubin

On Tue, Oct 20, 2009 at 4:59 PM, Jeff Moyer <jmoyer@...hat.com> wrote:
> Zubin Dittia <zubin@...tri.com> 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.
>
> Cheers,
> Jeff
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/