Re: Expected msgrcv(2) behaviour with msgsz > SSIZE_MAX ?

[christos%astron.com@localhost (Christos Zoulas)]

In article <20090125144448.GA86573%medusa.sis.pasteur.fr@localhost>,
Nicolas Joly  <njoly%pasteur.fr@localhost> wrote:
> 
>Index: lib/libc/sys/msgrcv.2
>===================================================================
>RCS file: /cvsroot/src/lib/libc/sys/msgrcv.2,v
>retrieving revision 1.17
>diff -u -p -r1.17 msgrcv.2
>--- lib/libc/sys/msgrcv.2      13 May 2004 10:20:58 -0000      1.17
>+++ lib/libc/sys/msgrcv.2      24 Jan 2009 13:41:05 -0000
>@@ -173,7 +173,8 @@ The message queue was removed while
> was waiting for a message of the requested type to become available in it.
> .Pp
> .Fa msgsz
>-is less than 0.
>+is greater than
>+.Dv SSIZE_MAX .
> .It Bq Er E2BIG
> A matching message was received, but its size was greater than
> .Fa msgsz
>Index: lib/libc/sys/msgsnd.2
>===================================================================
>RCS file: /cvsroot/src/lib/libc/sys/msgsnd.2,v
>retrieving revision 1.15
>diff -u -p -r1.15 msgsnd.2
>--- lib/libc/sys/msgsnd.2      13 May 2004 10:20:58 -0000      1.15
>+++ lib/libc/sys/msgsnd.2      24 Jan 2009 13:41:05 -0000
>@@ -141,8 +141,10 @@ was waiting for a resource to become ava
> message.
> .Pp
> .Fa msgsz
>-is less than 0, or greater than
>-.Va msg_qbytes .
>+is greater than
>+.Va msg_qbytes
>+or
>+.Dv SSIZE_MAX .
> .It Bq Er EACCES
> The calling process does not have write access to the message queue.
> .It Bq Er EAGAIN

Looks good, commit it.

christos