Do permission checks for a _IO_CONNECT_RENAME message
#include <sys/iofunc.h>
int iofunc_rename( resmgr_context_t* ctp,
io_rename_t* msg,
iofunc_attr_t* oldattr,
iofunc_attr_t* olddattr,
iofunc_attr_t* newattr,
iofunc_attr_t* newdattr,
struct _client_info* info );
libc
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The function iofunc_rename() does permission checks for the _IO_CONNECT message (subtype _IO_CONNECT_RENAME) for context ctp. The newattr argument is the attribute of the target if it already exists.
This function is similar to iofunc_open(). The iofunc_rename() function checks to see if the client (described by the optional info structure) has access to open the resource (name passed in the msg structure). The attr structure describes the resource's attributes.
The info argument can be passed as NULL, in which case iofunc_rename() obtains the client information itself via a call to iofunc_client_info_ext(). It is, of course, more efficient to get the client information once, rather than call this function with NULL every time.
io_rename_t structure
The io_rename_t structure holds the _IO_CONNECT message received by the resource manager:
typedef union {
struct _io_connect connect;
struct _io_connect_link_reply link_reply;
struct _io_connect_ftype_reply ftype_reply;
} io_rename_t;
This message structure is a union of an input message (coming to the resource manager), _io_connect, and two possible output or reply messages (going back to the client):
Or:
The reply includes the following extra information:
typedef union _io_rename_extra {
char path[1];
} io_rename_extra_t;
| Safety: | |
|---|---|
| Cancellation point | No |
| Interrupt handler | No |
| Signal handler | Yes |
| Thread | Yes |