Re: [patch] Clarified incompatibility and correct usage of XDR API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/24/2015 07:20 PM, saulery@xxxxxxx wrote:
> From: Stéphane Aulery <saulery@xxxxxxx>
> 
> Debian Bug #628099
> Report and patch of Taisuke Yamada <tai@xxxxxxxxxxxx>

Thanks, Stéphane. Applied.

Cheers,

Michael


> Signed-off-by: Stéphane Aulery <saulery@xxxxxxx>
> ---
>  man3/xdr.3 | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/man3/xdr.3 b/man3/xdr.3
> index 8f931db..f4bb3e9 100644
> --- a/man3/xdr.3
> +++ b/man3/xdr.3
> @@ -291,9 +291,11 @@ Note: the XDR stream's
>  .I op
>  field must be set by the caller.
>  .IP
> -Warning: this XDR stream implements an intermediate record stream.
> -Therefore there are additional bytes in the stream
> -to provide record boundary information.
> +Warning: To read from XDR stream created by this API, you'll need to
> +call xdrrec_skiprecord(3) first before calling any other XDR APIs.
> +This is because this inserts additional bytes in the stream to provide
> +record boundary information. Also, XDR streams created with different
> +xdr*_create APIs are not compatible for the same reason.
>  .LP
>  .nf
>  .BI "bool_t xdrrec_endofrecord(XDR *" xdrs ", int " sendnow );
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux