skb_has_shared_frag(9) [centos man page]

SKB_HAS_SHARED_FRAG(9)						 Linux Networking					    SKB_HAS_SHARED_FRAG(9)

NAME

       skb_has_shared_frag - can any frag be overwritten

SYNOPSIS

       bool skb_has_shared_frag(const struct sk_buff * skb);

ARGUMENTS

       skb
	   buffer to test

DESCRIPTION

       Return true if the skb has at least one frag that might be modified by an external entity (as in vmsplice/sendfile)

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						    SKB_HAS_SHARED_FRAG(9)

WIMAX_MSG_ALLOC(9)						 Linux Networking						WIMAX_MSG_ALLOC(9)

NAME

       wimax_msg_alloc - Create a new skb for sending a message to userspace

SYNOPSIS

       struct sk_buff * wimax_msg_alloc(struct wimax_dev * wimax_dev, const char * pipe_name, const void * msg, size_t size, gfp_t gfp_flags);

ARGUMENTS

       wimax_dev
	   WiMAX device descriptor

       pipe_name
	   "named pipe" the message will be sent to

       msg
	   pointer to the message data to send

       size
	   size of the message to send (in bytes), including the header.

       gfp_flags
	   flags for memory allocation.

RETURNS

       0 if ok, negative errno code on error

DESCRIPTION

       Allocates an skb that will contain the message to send to user space over the messaging pipe and initializes it, copying the payload.

       Once this call is done, you can deliver it with wimax_msg_send.

IMPORTANT

       Don't use skb_push/skb_pull/skb_reserve on the skb, as wimax_msg_send depends on skb->data being placed at the beginning of the user
       message.

       Unlike other WiMAX stack calls, this call can be used way early, even before wimax_dev_add is called, as long as the wimax_dev->net_dev
       pointer is set to point to a proper net_dev. This is so that drivers can use it early in case they need to send stuff around or communicate
       with user space.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							WIMAX_MSG_ALLOC(9)