rpc_gss_max_data_length(), rpc_gss_svc_max_data_length() — get maximum data length for transmission
struct svc_req *req,
Performing a security transformation on a piece of data generally produces
data with a different (usually greater) length.
For some transports, such as UDP, there is a maximum length of data
which can be sent out in one data unit.
Applications need to know the maximum size a piece of data can be
before it's transformed, so that the resulting data will still "fit"
on the transport.
You can use the following two functions to determine the maximum data length
is the client-side version, and
is the server-side version.
The following parameters can be used with these functions:
An RPC context handle of type
returned when a context is created (for example, by
Security service and QOP are bound to this handle, eliminating
any need to specify them.
The maximum size of a piece of data allowed by the transport.
A pointer to an RPC
structure, containing information on the context (for example,
program number and credentials).
- Thread Safe:
- Cancel Safe:
- Fork Safe:
- Async-cancel Safe:
- Async-signal Safe:
These functions can be called safely in a multithreaded environment.
They may be cancellation points in that they call functions that are
In a multithreaded environment, these functions are
not safe to be called by a child process after
These functions should not be called by a multithreaded application
that supports asynchronous cancellation or asynchronous signals.
Both functions return the maximum size of untransformed data
allowed, as an