blk_integrity_compare(9) [centos man page]

BLK_INTEGRITY_COMPAR(9) 					   Block Devices					   BLK_INTEGRITY_COMPAR(9)

NAME

       blk_integrity_compare - Compare integrity profile of two disks

SYNOPSIS

       int blk_integrity_compare(struct gendisk * gd1, struct gendisk * gd2);

ARGUMENTS

       gd1
	   Disk to compare

       gd2
	   Disk to compare

DESCRIPTION

       Meta-devices like DM and MD need to verify that all sub-devices use the same integrity format before advertising to upper layers that they
       can send/receive integrity metadata. This function can be used to check whether two gendisk devices have compatible integrity formats.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   BLK_INTEGRITY_COMPAR(9)

gss_unwrap(3)						     Library Functions Manual						     gss_unwrap(3)

NAME

       gss_unwrap - verify a message with attached message integrity code (MIC) and decrypt message content if necessary

SYNOPSIS


DESCRIPTION

       The routine converts a protected message to a usable form and verifies the embedded message integrity code (MIC).  The conf_state parameter
       indicates whether the message was encrypted.  The qop_state parameter indicates the quality of protection that was used to provide the con-
       fidentiality and integrity services.

   Input Parameters
       context_handle	     Specifies the context on which the message arrived.

       input_message_buffer  Specifies the protected message.

       output_message_buffer Specifies the buffer to receive the unwrapped message.

   Output Parameters
       conf_state	     Returns the requested level of confidentiality and integrity services, as follows:

			     Non-zero	 Both confidentiality and integrity services were used.

			     zero	 Only integrity services was used.

       qop_state	     Returns the cryptographic algorithm, or quality of protection.

       minor_status	     Returns a status code from the security mechanism.

STATUS CODES

       The following status codes can be returned:

       The routine was completed successfully.

       The signature was incorrect.

       The context has already expired.

       The context is recognized but the associated
				credentials have expired.

       The token failed consistency checks.

       The token was valid and contained the correct
				signature but it had already been processed.

       The routine failed.	The context specified in the context_handle parameter was not valid.

       The context identified in the
				context_handle parameter was not valid.

       The token was valid and contained the correct signature
				but it is too old.

       The token was valid, and contained a correct MIC
				for the message, but has been verified out of sequence; a later token has already been received.

       The token was valid, and contained a correct MIC
				for the message, but has been verified out of sequence; an earlier expected token has not yet been received.

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       gss_get_mic(3), gss_wrap(3).

																     gss_unwrap(3)