| 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
| ||
|
Message-ID: <x49ljj5og8q.fsf@segfault.boston.devel.redhat.com> Date: Tue, 20 Oct 2009 18:25:09 -0400 From: Jeff Moyer <jmoyer@...hat.com> To: Zubin Dittia <zubin@...tri.com> Cc: linux-kernel@...r.kernel.org Subject: Re: libaio asynchronous syscall io_getevents blocks on error Zubin Dittia <zubin@...tri.com> 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 -- 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/
Powered by blists - more mailing lists