On Wed, Jan 23, 2013 at 4:32 PM, Thomas Rast <tr...@student.ethz.ch> wrote:
> Erik Faye-Lund <kusmab...@gmail.com> writes:
>> On Tue, Jan 22, 2013 at 11:14 PM, Thomas Rast <tr...@student.ethz.ch> wrote:
>>> Eric Chamberland <eric.chamberl...@giref.ulaval.ca> writes:
>>> Other than that I agree with Junio, from what we've seen so far, Lustre
>>> returns EINTR on all sorts of calls that simply aren't allowed to do so.
>> I don't think this analysis is 100% accurate, POSIX allows error codes
>> to be generated other than those defined. From
>> http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_03.html:
>> "Implementations may support additional errors not included in this
>> list, *may generate errors included in this list under circumstances
>> other than those described here*, or may contain extensions or
>> limitations that prevent some errors from occurring."
> That same page says, however:
>   For functions under the Threads option for which [EINTR] is not listed
>   as a possible error condition in this volume of IEEE Std 1003.1-2001,
>   an implementation shall not return an error code of [EINTR].

Yes, but surely that's for pthreads functions, no? utime is not one of
those functions...
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to