This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] [PATCH] Make lio_listio set errno to EIO on requests with invalid aio_lio_opcode

From: Ulrich Drepper <drepper at redhat dot com>
To: Suzuki <suzuki at In dot ibm dot com>
Cc: libc-alpha at sources dot redhat dot com
Date: Sat, 25 Feb 2006 11:44:46 -0800
Subject: Re: [RFC] [PATCH] Make lio_listio set errno to EIO on requests with invalid aio_lio_opcode
References: <20060221013347.DCDD7180C28@magilla.sf.frob.com> <43FAC019.7020504@In.ibm.com> <20060221074453.GT4625@sunsite.mff.cuni.cz> <43FAD63D.3010000@In.ibm.com>

Suzuki wrote:
> If the opcode is not supported then that I/O operation should fail. For
> those requests, since we know that I/O operation has failed, even before
> enqueuing a request, shouldn't lio_listio() return EIO ?

No, there is no such requirement.  The current code is correct and if a
program has problems it is that program's fault.

-- 
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â

Attachment: signature.asc
Description: OpenPGP digital signature

References:
- Re: [RFC] [PATCH] Make lio_listio set errno to EIO on requests with invalid aio_lio_opcode
  - From: Roland McGrath
- Re: [RFC] [PATCH] Make lio_listio set errno to EIO on requests with invalid aio_lio_opcode
  - From: Suzuki
- Re: [RFC] [PATCH] Make lio_listio set errno to EIO on requests with invalid aio_lio_opcode
  - From: Jakub Jelinek
- Re: [RFC] [PATCH] Make lio_listio set errno to EIO on requests with invalid aio_lio_opcode
  - From: Suzuki

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