PATCH: aio_error() POSIX compliance
Ulrich Drepper
drepper@redhat.com
Thu Jun 13 16:59:00 GMT 2002
On Thu, 2002-06-13 at 15:52, Amos Waterland wrote:
> int aio_error(const struct aiocb *aiocbp);
>
> The aio_error() function may fail if:
>
> [EINVAL] The aiocbp argument does not refer to an asynchronous
> operation whose return status has not yet been retrieved.
>
> 1. Right now, glibc does not do any error checking for whether the aiocbp is
> invalid. For example, if aio_error() is passed a null pointer, it
> segfaults (see below for code listing for test0020.c):
>
> % ./test0020
> Segmentation fault
That's bogus. NULL is no reference to an aiocb structure. These kind
of tests are never necessary and are nowhere to be found in glibc. Fix
your "test suite".
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20020613/7aefcc3f/attachment.sig>
More information about the Libc-alpha
mailing list