This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: What should aio_fsync (O_SYNC, NULL) do?

To: Andreas Jaeger <aj at suse dot de>, GNU libc hacker <libc-hacker at sourceware dot cygnus dot com>
Subject: Re: What should aio_fsync (O_SYNC, NULL) do?
From: Mark Brown <bmark at us dot ibm dot com>
Date: Wed, 26 Jul 2000 10:34:45 -0500
References: <u8u2ddqa3c.fsf@gromit.rhein-neckar.de>

At 3:45 PM +0200 7/26/00, Andreas Jaeger wrote:
>Uli,
>
>I'm enhancing rt/tst-aio.c to test also aio_fsync.  My Posix Standard
>mentions (1003.1, 1996 Edition) on page 181 for aio_fsync:
>"If aiocb is NULL, then no status is returned..."
>
>Currently aio_fsync (O_SYNC, NULL) gives a segmentation fault.  The
>current Austin Draft does not mention NULL anymore.  Shall I add the
>test for NULL or not?

Andreas,

Under the rules that will govern the AG book, you may continue to handle
NULL as specified in the 1003.1-1996 book -- which I personally
prefer to a core dump :) All that the omission (if intentional)
means is that implementations can handle NULL as they see fit.

I will try to find out if this is intentional.

Mark Brown

-- 
-------------------------
Mark S. Brown                                                   bmark@us.ibm.com
IBM RS/6000 AIX System Architecture                    512.838.3926  T/L678.3926
IBM Corporation, Austin, Texas

Follow-Ups:
- Re: What should aio_fsync (O_SYNC, NULL) do?
  - From: Andreas Jaeger

References:
- What should aio_fsync (O_SYNC, NULL) do?
  - From: Andreas Jaeger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]