Re: [PATCH] 2.4.19-pre3 - readv/writev should return EINVAL for count=0

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Wed Mar 20 2002 - 18:48:00 EST

Next message: Tom Epperly: "Re: Bad Illegal instruction traps on dual-Xeon (p4) Linux Dell box"
Previous message: Kurt Garloff: "Re: Bad Illegal instruction traps on dual-Xeon (p4) Linux Dell box"
In reply to: Paul Larson: "[PATCH] 2.4.19-pre3 - readv/writev should return EINVAL for count=0"
Next in thread: Alex Riesen: "Re: [PATCH] 2.4.19-pre3 - readv/writev should return EINVAL for count=0"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> This is a minor patch against 2.4.19-pre3 for readv/writev to have it
> return EINVAL if count=0 is passed to it. According to the man page and
> also the specifications for readv/writev, this is the correct behaviour.

I beg to disagree. The existing behaviour is compliant. The behaviour for
writing/reading 0 may optionally return -EINVAL. (Single Unix Spec v3).

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Tom Epperly: "Re: Bad Illegal instruction traps on dual-Xeon (p4) Linux Dell box"
Previous message: Kurt Garloff: "Re: Bad Illegal instruction traps on dual-Xeon (p4) Linux Dell box"
In reply to: Paul Larson: "[PATCH] 2.4.19-pre3 - readv/writev should return EINVAL for count=0"
Next in thread: Alex Riesen: "Re: [PATCH] 2.4.19-pre3 - readv/writev should return EINVAL for count=0"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:23 EST