€•â     Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ4/translations/zh_CN/admin-guide/device-mapper/dm-ima”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ4/translations/zh_TW/admin-guide/device-mapper/dm-ima”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ4/translations/it_IT/admin-guide/device-mapper/dm-ima”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ4/translations/ja_JP/admin-guide/device-mapper/dm-ima”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ4/translations/ko_KR/admin-guide/device-mapper/dm-ima”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ4/translations/sp_SP/admin-guide/device-mapper/dm-ima”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒdm-ima”h]”hŒdm-ima”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒN/var/lib/git/docbuild/linux/Documentation/admin-guide/device-mapper/dm-ima.rst”h KubhŒ	paragraph”“”)”}”(hX±  For a given system, various external services/infrastructure tools
(including the attestation service) interact with it - both during the
setup and during rest of the system run-time.  They share sensitive data
and/or execute critical workload on that system.  The external services
may want to verify the current run-time state of the relevant kernel
subsystems before fully trusting the system with business-critical
data/workload.”h]”hX±  For a given system, various external services/infrastructure tools
(including the attestation service) interact with it - both during the
setup and during rest of the system run-time.  They share sensitive data
and/or execute critical workload on that system.  The external services
may want to verify the current run-time state of the relevant kernel
subsystems before fully trusting the system with business-critical
data/workload.”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hX.  Device mapper plays a critical role on a given system by providing
various important functionalities to the block devices using various
target types like crypt, verity, integrity etc.  Each of these target
typesâ€™ functionalities can be configured with various attributes.
The attributes chosen to configure these target types can significantly
impact the security profile of the block device, and in-turn, of the
system itself.  For instance, the type of encryption algorithm and the
key size determines the strength of encryption for a given block device.”h]”hX.  Device mapper plays a critical role on a given system by providing
various important functionalities to the block devices using various
target types like crypt, verity, integrity etc.  Each of these target
typesâ€™ functionalities can be configured with various attributes.
The attributes chosen to configure these target types can significantly
impact the security profile of the block device, and in-turn, of the
system itself.  For instance, the type of encryption algorithm and the
key size determines the strength of encryption for a given block device.”…””}”(hhÇhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒÒTherefore, verifying the current state of various block devices as well
as their various target attributes is crucial for external services before
fully trusting the system with business-critical data/workload.”h]”hŒÒTherefore, verifying the current state of various block devices as well
as their various target attributes is crucial for external services before
fully trusting the system with business-critical data/workload.”…””}”(hhÕhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒIMA kernel subsystem provides the necessary functionality for
device mapper to measure the state and configuration of
various block devices -”h]”hŒIMA kernel subsystem provides the necessary functionality for
device mapper to measure the state and configuration of
various block devices -”…””}”(hhãhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ0by device mapper itself, from within the kernel,”h]”h¸)”}”(hhúh]”hŒ0by device mapper itself, from within the kernel,”…””}”(hhühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhøubah}”(h]”h ]”h"]”h$]”h&]”uh1höhhóhžhhŸh¶h Nubh÷)”}”(hŒin a tamper resistant way,”h]”h¸)”}”(hj  h]”hŒin a tamper resistant way,”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhhóhžhhŸh¶h Nubh÷)”}”(hŒ;and re-measured - triggered on state/configuration change.
”h]”h¸)”}”(hŒ:and re-measured - triggered on state/configuration change.”h]”hŒ:and re-measured - triggered on state/configuration change.”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K hj&  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhhóhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hñhŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒSetting the IMA Policy:”h]”hŒSetting the IMA Policy:”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjF  hžhhŸh¶h K#ubh¸)”}”(hŒÁFor IMA to measure the data on a given system, the IMA policy on the
system needs to be updated to have following line, and the system needs
to be restarted for the measurements to take effect.”h]”hŒÁFor IMA to measure the data on a given system, the IMA policy on the
system needs to be updated to have following line, and the system needs
to be restarted for the measurements to take effect.”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K$hjF  hžhubhŒliteral_block”“”)”}”(hŒV/etc/ima/ima-policy
   measure func=CRITICAL_DATA label=device-mapper template=ima-buf”h]”hŒV/etc/ima/ima-policy
   measure func=CRITICAL_DATA label=device-mapper template=ima-buf”…””}”hjg  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1je  hŸh¶h K*hjF  hžhubh¸)”}”(hŒIThe measurements will be reflected in the IMA logs, which are located at:”h]”hŒIThe measurements will be reflected in the IMA logs, which are located at:”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K-hjF  hžhubjf  )”}”(hŒ|/sys/kernel/security/integrity/ima/ascii_runtime_measurements
/sys/kernel/security/integrity/ima/binary_runtime_measurements”h]”hŒ|/sys/kernel/security/integrity/ima/ascii_runtime_measurements
/sys/kernel/security/integrity/ima/binary_runtime_measurements”…””}”hj…  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h K1hjF  hžhubh¸)”}”(hŒ8Then IMA ASCII measurement log has the following format:”h]”hŒ8Then IMA ASCII measurement log has the following format:”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K4hjF  hžhubjf  )”}”(hXÌ  <PCR> <TEMPLATE_DATA_DIGEST> <TEMPLATE_NAME> <TEMPLATE_DATA>

PCR := Platform Configuration Register, in which the values are registered.
      This is applicable if TPM chip is in use.

TEMPLATE_DATA_DIGEST := Template data digest of the IMA record.
TEMPLATE_NAME := Template name that registered the integrity value (e.g. ima-buf).

TEMPLATE_DATA := <ALG> ":" <EVENT_DIGEST> <EVENT_NAME> <EVENT_DATA>
                 It contains data for the specific event to be measured,
                 in a given template data format.

ALG := Algorithm to compute event digest
EVENT_DIGEST := Digest of the event data
EVENT_NAME := Description of the event (e.g. 'dm_table_load').
EVENT_DATA := The event data to be measured.”h]”hXÌ  <PCR> <TEMPLATE_DATA_DIGEST> <TEMPLATE_NAME> <TEMPLATE_DATA>

PCR := Platform Configuration Register, in which the values are registered.
      This is applicable if TPM chip is in use.

TEMPLATE_DATA_DIGEST := Template data digest of the IMA record.
TEMPLATE_NAME := Template name that registered the integrity value (e.g. ima-buf).

TEMPLATE_DATA := <ALG> ":" <EVENT_DIGEST> <EVENT_NAME> <EVENT_DATA>
                 It contains data for the specific event to be measured,
                 in a given template data format.

ALG := Algorithm to compute event digest
EVENT_DIGEST := Digest of the event data
EVENT_NAME := Description of the event (e.g. 'dm_table_load').
EVENT_DATA := The event data to be measured.”…””}”hj¡  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h K8hjF  hžhubhŒ
line_block”“”)”}”(hhh]”hh “”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hj±  hžhhŸh¶h K Œindent”K ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¯  hjF  hžhhŸh¶h KIubj°  )”}”(hhh]”(j´  )”}”(hŒ
*NOTE #1:*”h]”hŒemphasis”“”)”}”(hjÊ  h]”hŒNOTE #1:”…””}”(hjÎ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ  hjÈ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1h j¾  K hjÅ  hžhhŸh¶h KKubj´  )”}”(hŒ•The DM target data measured by IMA subsystem can alternatively
be queried from userspace by setting DM_IMA_MEASUREMENT_FLAG with
DM_TABLE_STATUS_CMD.”h]”hŒ•The DM target data measured by IMA subsystem can alternatively
be queried from userspace by setting DM_IMA_MEASUREMENT_FLAG with
DM_TABLE_STATUS_CMD.”…””}”(hjá  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h j¾  K hjÅ  hžhhŸh¶h KNubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¯  hjF  hžhhŸh¶h KKubj°  )”}”(hhh]”j´  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1h hjõ  hžhhŸh¶h K j¾  K ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¯  hjF  hžhhŸh¶h KPubj°  )”}”(hhh]”(j´  )”}”(hŒ
*NOTE #2:*”h]”jÍ  )”}”(hj  h]”hŒNOTE #2:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÌ  hj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1h j¾  K hj  hžhhŸh¶h KRubj´  )”}”(hŒ[The Kernel configuration CONFIG_IMA_DISABLE_HTABLE allows measurement of duplicate records.”h]”hŒ[The Kernel configuration CONFIG_IMA_DISABLE_HTABLE allows measurement of duplicate records.”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h j¾  K hj  hžhhŸh¶h KSubj´  )”}”(hŒ}To support recording duplicate IMA events in the IMA log, the Kernel needs to be configured with
CONFIG_IMA_DISABLE_HTABLE=y.”h]”hŒ}To support recording duplicate IMA events in the IMA log, the Kernel needs to be configured with
CONFIG_IMA_DISABLE_HTABLE=y.”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h j¾  K hj  hžhhŸh¶h KUubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¯  hjF  hžhhŸh¶h KRubeh}”(h]”Œsetting-the-ima-policy”ah ]”h"]”Œsetting the ima policy:”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K#ubh¢)”}”(hhh]”(h§)”}”(hŒSupported Device States:”h]”hŒSupported Device States:”…””}”(hjN  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjK  hžhhŸh¶h KXubh¸)”}”(hŒ=Following device state changes will trigger IMA measurements:”h]”hŒ=Following device state changes will trigger IMA measurements:”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KYhjK  hžhubhŒblock_quote”“”)”}”(hŒP1. Table load
#. Device resume
#. Device remove
#. Table clear
#. Device rename
”h]”hŒenumerated_list”“”)”}”(hhh]”(h÷)”}”(hŒ
Table load”h]”h¸)”}”(hjw  h]”hŒ
Table load”…””}”(hjy  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K[hju  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjr  ubh÷)”}”(hŒDevice resume”h]”h¸)”}”(hjŽ  h]”hŒDevice resume”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K\hjŒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjr  ubh÷)”}”(hŒDevice remove”h]”h¸)”}”(hj¥  h]”hŒDevice remove”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K]hj£  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjr  ubh÷)”}”(hŒTable clear”h]”h¸)”}”(hj¼  h]”hŒTable clear”…””}”(hj¾  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K^hjº  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjr  ubh÷)”}”(hŒDevice rename
”h]”h¸)”}”(hŒDevice rename”h]”hŒDevice rename”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K_hjÑ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjr  ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1jp  hjl  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jj  hŸh¶h K[hjK  hžhubh¢)”}”(hhh]”(h§)”}”(hŒ1. Table load:”h]”hŒ1. Table load:”…””}”(hjý  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjú  hžhhŸh¶h Kbubh¸)”}”(hŒœWhen a new table is loaded in a device's inactive table slot,
the device information and target specific details from the
targets in the table are measured.”h]”hŒžWhen a new table is loaded in a deviceâ€™s inactive table slot,
the device information and target specific details from the
targets in the table are measured.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kchjú  hžhubh¸)”}”(hŒEThe IMA measurement log has the following format for 'dm_table_load':”h]”hŒIThe IMA measurement log has the following format for â€˜dm_table_loadâ€™:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kghjú  hžhubjf  )”}”(hXí  EVENT_NAME := "dm_table_load"
EVENT_DATA := <dm_version_str> ";" <device_metadata> ";" <table_load_data>

dm_version_str := "dm_version=" <N> "." <N> "." <N>
                 Same as Device Mapper driver version.
device_metadata := <device_name> "," <device_uuid> "," <device_major> "," <device_minor> ","
                  <minor_count> "," <num_device_targets> ";"

device_name := "name=" <dm-device-name>
device_uuid := "uuid=" <dm-device-uuid>
device_major := "major=" <N>
device_minor := "minor=" <N>
minor_count := "minor_count=" <N>
num_device_targets := "num_targets=" <N>
dm-device-name := Name of the device. If it contains special characters like '\', ',', ';',
                  they are prefixed with '\'.
dm-device-uuid := UUID of the device. If it contains special characters like '\', ',', ';',
                  they are prefixed with '\'.

table_load_data := <target_data>
                   Represents the data (as name=value pairs) from various targets in the table,
                   which is being loaded into the DM device's inactive table slot.
target_data := <target_data_row> | <target_data><target_data_row>

target_data_row := <target_index> "," <target_begin> "," <target_len> "," <target_name> ","
                   <target_version> "," <target_attributes> ";"
target_index := "target_index=" <N>
                Represents nth target in the table (from 0 to N-1 targets specified in <num_device_targets>)
                If all the data for N targets doesn't fit in the given buffer - then the data that fits
                in the buffer (say from target 0 to x) is measured in a given IMA event.
                The remaining data from targets x+1 to N-1 is measured in the subsequent IMA events,
                with the same format as that of 'dm_table_load'
                i.e. <dm_version_str> ";" <device_metadata> ";" <table_load_data>.

target_begin := "target_begin=" <N>
target_len := "target_len=" <N>
target_name := Name of the target. 'linear', 'crypt', 'integrity' etc.
               The targets that are supported for IMA measurements are documented below in the
               'Supported targets' section.
target_version := "target_version=" <N> "." <N> "." <N>
target_attributes := Data containing comma separated list of name=value pairs of target specific attributes.

For instance, if a linear device is created with the following table entries,
 # dmsetup create linear1
 0 2 linear /dev/loop0 512
 2 2 linear /dev/loop0 512
 4 2 linear /dev/loop0 512
 6 2 linear /dev/loop0 512

Then IMA ASCII measurement log will have the following entry:
(converted from ASCII to text for readability)

10 a8c5ff755561c7a28146389d1514c318592af49a ima-buf sha256:4d73481ecce5eadba8ab084640d85bb9ca899af4d0a122989252a76efadc5b72
dm_table_load
dm_version=4.45.0;
name=linear1,uuid=,major=253,minor=0,minor_count=1,num_targets=4;
target_index=0,target_begin=0,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;
target_index=1,target_begin=2,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;
target_index=2,target_begin=4,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;
target_index=3,target_begin=6,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;”h]”hXí  EVENT_NAME := "dm_table_load"
EVENT_DATA := <dm_version_str> ";" <device_metadata> ";" <table_load_data>

dm_version_str := "dm_version=" <N> "." <N> "." <N>
                 Same as Device Mapper driver version.
device_metadata := <device_name> "," <device_uuid> "," <device_major> "," <device_minor> ","
                  <minor_count> "," <num_device_targets> ";"

device_name := "name=" <dm-device-name>
device_uuid := "uuid=" <dm-device-uuid>
device_major := "major=" <N>
device_minor := "minor=" <N>
minor_count := "minor_count=" <N>
num_device_targets := "num_targets=" <N>
dm-device-name := Name of the device. If it contains special characters like '\', ',', ';',
                  they are prefixed with '\'.
dm-device-uuid := UUID of the device. If it contains special characters like '\', ',', ';',
                  they are prefixed with '\'.

table_load_data := <target_data>
                   Represents the data (as name=value pairs) from various targets in the table,
                   which is being loaded into the DM device's inactive table slot.
target_data := <target_data_row> | <target_data><target_data_row>

target_data_row := <target_index> "," <target_begin> "," <target_len> "," <target_name> ","
                   <target_version> "," <target_attributes> ";"
target_index := "target_index=" <N>
                Represents nth target in the table (from 0 to N-1 targets specified in <num_device_targets>)
                If all the data for N targets doesn't fit in the given buffer - then the data that fits
                in the buffer (say from target 0 to x) is measured in a given IMA event.
                The remaining data from targets x+1 to N-1 is measured in the subsequent IMA events,
                with the same format as that of 'dm_table_load'
                i.e. <dm_version_str> ";" <device_metadata> ";" <table_load_data>.

target_begin := "target_begin=" <N>
target_len := "target_len=" <N>
target_name := Name of the target. 'linear', 'crypt', 'integrity' etc.
               The targets that are supported for IMA measurements are documented below in the
               'Supported targets' section.
target_version := "target_version=" <N> "." <N> "." <N>
target_attributes := Data containing comma separated list of name=value pairs of target specific attributes.

For instance, if a linear device is created with the following table entries,
 # dmsetup create linear1
 0 2 linear /dev/loop0 512
 2 2 linear /dev/loop0 512
 4 2 linear /dev/loop0 512
 6 2 linear /dev/loop0 512

Then IMA ASCII measurement log will have the following entry:
(converted from ASCII to text for readability)

10 a8c5ff755561c7a28146389d1514c318592af49a ima-buf sha256:4d73481ecce5eadba8ab084640d85bb9ca899af4d0a122989252a76efadc5b72
dm_table_load
dm_version=4.45.0;
name=linear1,uuid=,major=253,minor=0,minor_count=1,num_targets=4;
target_index=0,target_begin=0,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;
target_index=1,target_begin=2,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;
target_index=2,target_begin=4,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;
target_index=3,target_begin=6,target_len=2,target_name=linear,target_version=1.4.0,device_name=7:0,start=512;”…””}”hj'  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h Kkhjú  hžhubeh}”(h]”Œ
table-load”ah ]”h"]”Œ1. table load:”ah$]”h&]”uh1h¡hjK  hžhhŸh¶h Kbubh¢)”}”(hhh]”(h§)”}”(hŒ2. Device resume:”h]”hŒ2. Device resume:”…””}”(hj@  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj=  hžhhŸh¶h K©ubh¸)”}”(hŒ‡When a suspended device is resumed, the device information and the hash of the
data from previous load of an active table are measured.”h]”hŒ‡When a suspended device is resumed, the device information and the hash of the
data from previous load of an active table are measured.”…””}”(hjN  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kªhj=  hžhubh¸)”}”(hŒHThe IMA measurement log has the following format for 'dm_device_resume':”h]”hŒLThe IMA measurement log has the following format for â€˜dm_device_resumeâ€™:”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K­hj=  hžhubjf  )”}”(hX8  EVENT_NAME := "dm_device_resume"
EVENT_DATA := <dm_version_str> ";" <device_metadata> ";" <active_table_hash> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_metadata := As described in the 'Table load' section above.
active_table_hash := "active_table_hash=" <table_hash_alg> ":" <table_hash>
                     Rerpresents the hash of the IMA data being measured for the
                     active table for the device.
table_hash_alg := Algorithm used to compute the hash.
table_hash := Hash of the (<dm_version_str> ";" <device_metadata> ";" <table_load_data> ";")
              as described in the 'dm_table_load' above.
              Note: If the table_load data spans across multiple IMA 'dm_table_load'
              events for a given device, the hash is computed combining all the event data
              i.e. (<dm_version_str> ";" <device_metadata> ";" <table_load_data> ";")
              across all those events.
current_device_capacity := "current_device_capacity=" <N>

For instance, if a linear device is resumed with the following command,
#dmsetup resume linear1

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 56c00cc062ffc24ccd9ac2d67d194af3282b934e ima-buf sha256:e7d12c03b958b4e0e53e7363a06376be88d98a1ac191fdbd3baf5e4b77f329b6
dm_device_resume
dm_version=4.45.0;
name=linear1,uuid=,major=253,minor=0,minor_count=1,num_targets=4;
active_table_hash=sha256:4d73481ecce5eadba8ab084640d85bb9ca899af4d0a122989252a76efadc5b72;current_device_capacity=8;”h]”hX8  EVENT_NAME := "dm_device_resume"
EVENT_DATA := <dm_version_str> ";" <device_metadata> ";" <active_table_hash> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_metadata := As described in the 'Table load' section above.
active_table_hash := "active_table_hash=" <table_hash_alg> ":" <table_hash>
                     Rerpresents the hash of the IMA data being measured for the
                     active table for the device.
table_hash_alg := Algorithm used to compute the hash.
table_hash := Hash of the (<dm_version_str> ";" <device_metadata> ";" <table_load_data> ";")
              as described in the 'dm_table_load' above.
              Note: If the table_load data spans across multiple IMA 'dm_table_load'
              events for a given device, the hash is computed combining all the event data
              i.e. (<dm_version_str> ";" <device_metadata> ";" <table_load_data> ";")
              across all those events.
current_device_capacity := "current_device_capacity=" <N>

For instance, if a linear device is resumed with the following command,
#dmsetup resume linear1

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 56c00cc062ffc24ccd9ac2d67d194af3282b934e ima-buf sha256:e7d12c03b958b4e0e53e7363a06376be88d98a1ac191fdbd3baf5e4b77f329b6
dm_device_resume
dm_version=4.45.0;
name=linear1,uuid=,major=253,minor=0,minor_count=1,num_targets=4;
active_table_hash=sha256:4d73481ecce5eadba8ab084640d85bb9ca899af4d0a122989252a76efadc5b72;current_device_capacity=8;”…””}”hjj  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h K±hj=  hžhubeh}”(h]”Œdevice-resume”ah ]”h"]”Œ2. device resume:”ah$]”h&]”uh1h¡hjK  hžhhŸh¶h K©ubh¢)”}”(hhh]”(h§)”}”(hŒ3. Device remove:”h]”hŒ3. Device remove:”…””}”(hjƒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj€  hžhhŸh¶h KÏubh¸)”}”(hŒ~When a device is removed, the device information and a sha256 hash of the
data from an active and inactive table are measured.”h]”hŒ~When a device is removed, the device information and a sha256 hash of the
data from an active and inactive table are measured.”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÐhj€  hžhubh¸)”}”(hŒHThe IMA measurement log has the following format for 'dm_device_remove':”h]”hŒLThe IMA measurement log has the following format for â€˜dm_device_removeâ€™:”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÓhj€  hžhubjf  )”}”(hX{  EVENT_NAME := "dm_device_remove"
EVENT_DATA := <dm_version_str> ";" <device_active_metadata> ";" <device_inactive_metadata> ";"
              <active_table_hash> "," <inactive_table_hash> "," <remove_all> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_active_metadata := Device metadata that reflects the currently loaded active table.
                          The format is same as 'device_metadata' described in the 'Table load' section above.
device_inactive_metadata := Device metadata that reflects the inactive table.
                            The format is same as 'device_metadata' described in the 'Table load' section above.
active_table_hash := Hash of the currently loaded active table.
                     The format is same as 'active_table_hash' described in the 'Device resume' section above.
inactive_table_hash :=  Hash of the inactive table.
                        The format is same as 'active_table_hash' described in the 'Device resume' section above.
remove_all := "remove_all=" <yes_no>
yes_no := "y" | "n"
current_device_capacity := "current_device_capacity=" <N>

For instance, if a linear device is removed with the following command,
 #dmsetup remove l1

then IMA ASCII measurement log will have the following entry:
(converted from ASCII to text for readability)

10 790e830a3a7a31590824ac0642b3b31c2d0e8b38 ima-buf sha256:ab9f3c959367a8f5d4403d6ce9c3627dadfa8f9f0e7ec7899299782388de3840
dm_device_remove
dm_version=4.45.0;
device_active_metadata=name=l1,uuid=,major=253,minor=2,minor_count=1,num_targets=2;
device_inactive_metadata=name=l1,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
active_table_hash=sha256:4a7e62efaebfc86af755831998b7db6f59b60d23c9534fb16a4455907957953a,
inactive_table_hash=sha256:9d79c175bc2302d55a183e8f50ad4bafd60f7692fd6249e5fd213e2464384b86,remove_all=n;
current_device_capacity=2048;”h]”hX{  EVENT_NAME := "dm_device_remove"
EVENT_DATA := <dm_version_str> ";" <device_active_metadata> ";" <device_inactive_metadata> ";"
              <active_table_hash> "," <inactive_table_hash> "," <remove_all> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_active_metadata := Device metadata that reflects the currently loaded active table.
                          The format is same as 'device_metadata' described in the 'Table load' section above.
device_inactive_metadata := Device metadata that reflects the inactive table.
                            The format is same as 'device_metadata' described in the 'Table load' section above.
active_table_hash := Hash of the currently loaded active table.
                     The format is same as 'active_table_hash' described in the 'Device resume' section above.
inactive_table_hash :=  Hash of the inactive table.
                        The format is same as 'active_table_hash' described in the 'Device resume' section above.
remove_all := "remove_all=" <yes_no>
yes_no := "y" | "n"
current_device_capacity := "current_device_capacity=" <N>

For instance, if a linear device is removed with the following command,
 #dmsetup remove l1

then IMA ASCII measurement log will have the following entry:
(converted from ASCII to text for readability)

10 790e830a3a7a31590824ac0642b3b31c2d0e8b38 ima-buf sha256:ab9f3c959367a8f5d4403d6ce9c3627dadfa8f9f0e7ec7899299782388de3840
dm_device_remove
dm_version=4.45.0;
device_active_metadata=name=l1,uuid=,major=253,minor=2,minor_count=1,num_targets=2;
device_inactive_metadata=name=l1,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
active_table_hash=sha256:4a7e62efaebfc86af755831998b7db6f59b60d23c9534fb16a4455907957953a,
inactive_table_hash=sha256:9d79c175bc2302d55a183e8f50ad4bafd60f7692fd6249e5fd213e2464384b86,remove_all=n;
current_device_capacity=2048;”…””}”hj­  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h K×hj€  hžhubeh}”(h]”Œdevice-remove”ah ]”h"]”Œ3. device remove:”ah$]”h&]”uh1h¡hjK  hžhhŸh¶h KÏubh¢)”}”(hhh]”(h§)”}”(hŒ4. Table clear:”h]”hŒ4. Table clear:”…””}”(hjÆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÃ  hžhhŸh¶h Køubh¸)”}”(hŒŒWhen an inactive table is cleared from the device, the device information and a sha256 hash of the
data from an inactive table are measured.”h]”hŒŒWhen an inactive table is cleared from the device, the device information and a sha256 hash of the
data from an inactive table are measured.”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KùhjÃ  hžhubh¸)”}”(hŒFThe IMA measurement log has the following format for 'dm_table_clear':”h]”hŒJThe IMA measurement log has the following format for â€˜dm_table_clearâ€™:”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KühjÃ  hžhubjf  )”}”(hXÉ  EVENT_NAME := "dm_table_clear"
EVENT_DATA := <dm_version_str> ";" <device_inactive_metadata> ";" <inactive_table_hash> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_inactive_metadata := Device metadata that was captured during the load time inactive table being cleared.
                            The format is same as 'device_metadata' described in the 'Table load' section above.
inactive_table_hash := Hash of the inactive table being cleared from the device.
                       The format is same as 'active_table_hash' described in the 'Device resume' section above.
current_device_capacity := "current_device_capacity=" <N>

For instance, if a linear device's inactive table is cleared,
 #dmsetup clear l1

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 77d347408f557f68f0041acb0072946bb2367fe5 ima-buf sha256:42f9ca22163fdfa548e6229dece2959bc5ce295c681644240035827ada0e1db5
dm_table_clear
dm_version=4.45.0;
name=l1,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
inactive_table_hash=sha256:75c0dc347063bf474d28a9907037eba060bfe39d8847fc0646d75e149045d545;current_device_capacity=1024;”h]”hXÉ  EVENT_NAME := "dm_table_clear"
EVENT_DATA := <dm_version_str> ";" <device_inactive_metadata> ";" <inactive_table_hash> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_inactive_metadata := Device metadata that was captured during the load time inactive table being cleared.
                            The format is same as 'device_metadata' described in the 'Table load' section above.
inactive_table_hash := Hash of the inactive table being cleared from the device.
                       The format is same as 'active_table_hash' described in the 'Device resume' section above.
current_device_capacity := "current_device_capacity=" <N>

For instance, if a linear device's inactive table is cleared,
 #dmsetup clear l1

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 77d347408f557f68f0041acb0072946bb2367fe5 ima-buf sha256:42f9ca22163fdfa548e6229dece2959bc5ce295c681644240035827ada0e1db5
dm_table_clear
dm_version=4.45.0;
name=l1,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
inactive_table_hash=sha256:75c0dc347063bf474d28a9907037eba060bfe39d8847fc0646d75e149045d545;current_device_capacity=1024;”…””}”hjð  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M hjÃ  hžhubeh}”(h]”Œtable-clear”ah ]”h"]”Œ4. table clear:”ah$]”h&]”uh1h¡hjK  hžhhŸh¶h Køubh¢)”}”(hhh]”(h§)”}”(hŒ5. Device rename:”h]”hŒ5. Device rename:”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h Mubh¸)”}”(hŒhWhen an device's NAME or UUID is changed, the device information and the new NAME and UUID
are measured.”h]”hŒjWhen an deviceâ€™s NAME or UUID is changed, the device information and the new NAME and UUID
are measured.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj  hžhubh¸)”}”(hŒHThe IMA measurement log has the following format for 'dm_device_rename':”h]”hŒLThe IMA measurement log has the following format for â€˜dm_device_renameâ€™:”…””}”(hj%  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj  hžhubjf  )”}”(hX   EVENT_NAME := "dm_device_rename"
EVENT_DATA := <dm_version_str> ";" <device_active_metadata> ";" <new_device_name> "," <new_device_uuid> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_active_metadata := Device metadata that reflects the currently loaded active table.
                          The format is same as 'device_metadata' described in the 'Table load' section above.
new_device_name := "new_name=" <dm-device-name>
dm-device-name := Same as <dm-device-name> described in 'Table load' section above
new_device_uuid := "new_uuid=" <dm-device-uuid>
dm-device-uuid := Same as <dm-device-uuid> described in 'Table load' section above
current_device_capacity := "current_device_capacity=" <N>

E.g 1: if a linear device's name is changed with the following command,
 #dmsetup rename linear1 --setuuid 1234-5678

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 8b0423209b4c66ac1523f4c9848c9b51ee332f48 ima-buf sha256:6847b7258134189531db593e9230b257c84f04038b5a18fd2e1473860e0569ac
dm_device_rename
dm_version=4.45.0;
name=linear1,uuid=,major=253,minor=2,minor_count=1,num_targets=1;new_name=linear1,new_uuid=1234-5678;
current_device_capacity=1024;

E.g 2:  if a linear device's name is changed with the following command,
 # dmsetup rename linear1 linear=2

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 bef70476b99c2bdf7136fae033aa8627da1bf76f ima-buf sha256:8c6f9f53b9ef9dc8f92a2f2cca8910e622543d0f0d37d484870cb16b95111402
dm_device_rename
dm_version=4.45.0;
name=linear1,uuid=1234-5678,major=253,minor=2,minor_count=1,num_targets=1;
new_name=linear\=2,new_uuid=1234-5678;
current_device_capacity=1024;”h]”hX   EVENT_NAME := "dm_device_rename"
EVENT_DATA := <dm_version_str> ";" <device_active_metadata> ";" <new_device_name> "," <new_device_uuid> ";" <current_device_capacity> ";"

dm_version_str := As described in the 'Table load' section above.
device_active_metadata := Device metadata that reflects the currently loaded active table.
                          The format is same as 'device_metadata' described in the 'Table load' section above.
new_device_name := "new_name=" <dm-device-name>
dm-device-name := Same as <dm-device-name> described in 'Table load' section above
new_device_uuid := "new_uuid=" <dm-device-uuid>
dm-device-uuid := Same as <dm-device-uuid> described in 'Table load' section above
current_device_capacity := "current_device_capacity=" <N>

E.g 1: if a linear device's name is changed with the following command,
 #dmsetup rename linear1 --setuuid 1234-5678

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 8b0423209b4c66ac1523f4c9848c9b51ee332f48 ima-buf sha256:6847b7258134189531db593e9230b257c84f04038b5a18fd2e1473860e0569ac
dm_device_rename
dm_version=4.45.0;
name=linear1,uuid=,major=253,minor=2,minor_count=1,num_targets=1;new_name=linear1,new_uuid=1234-5678;
current_device_capacity=1024;

E.g 2:  if a linear device's name is changed with the following command,
 # dmsetup rename linear1 linear=2

then IMA ASCII measurement log will have an entry with:
(converted from ASCII to text for readability)

10 bef70476b99c2bdf7136fae033aa8627da1bf76f ima-buf sha256:8c6f9f53b9ef9dc8f92a2f2cca8910e622543d0f0d37d484870cb16b95111402
dm_device_rename
dm_version=4.45.0;
name=linear1,uuid=1234-5678,major=253,minor=2,minor_count=1,num_targets=1;
new_name=linear\=2,new_uuid=1234-5678;
current_device_capacity=1024;”…””}”hj3  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h Mhj  hžhubeh}”(h]”Œdevice-rename”ah ]”h"]”Œ5. device rename:”ah$]”h&]”uh1h¡hjK  hžhhŸh¶h Mubeh}”(h]”Œsupported-device-states”ah ]”h"]”Œsupported device states:”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KXubh¢)”}”(hhh]”(h§)”}”(hŒSupported targets:”h]”hŒSupported targets:”…””}”(hjT  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjQ  hžhhŸh¶h MEubh¸)”}”(hŒ@Following targets are supported to measure their data using IMA:”h]”hŒ@Following targets are supported to measure their data using IMA:”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MGhjQ  hžhubjk  )”}”(hŒi1. cache
#. crypt
#. integrity
#. linear
#. mirror
#. multipath
#. raid
#. snapshot
#. striped
#. verity
”h]”jq  )”}”(hhh]”(h÷)”}”(hŒcache”h]”h¸)”}”(hjy  h]”hŒcache”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MIhjw  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒcrypt”h]”h¸)”}”(hj  h]”hŒcrypt”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MJhjŽ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒ	integrity”h]”h¸)”}”(hj§  h]”hŒ	integrity”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MKhj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒlinear”h]”h¸)”}”(hj¾  h]”hŒlinear”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MLhj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒmirror”h]”h¸)”}”(hjÕ  h]”hŒmirror”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MMhjÓ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒ	multipath”h]”h¸)”}”(hjì  h]”hŒ	multipath”…””}”(hjî  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MNhjê  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒraid”h]”h¸)”}”(hj  h]”hŒraid”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MOhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒsnapshot”h]”h¸)”}”(hj  h]”hŒsnapshot”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MPhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒstriped”h]”h¸)”}”(hj1  h]”hŒstriped”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MQhj/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubh÷)”}”(hŒverity
”h]”h¸)”}”(hŒverity”h]”hŒverity”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MRhjF  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhjt  ubeh}”(h]”h ]”h"]”h$]”h&]”jï  jð  jñ  hjò  jó  uh1jp  hjp  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jj  hŸh¶h MIhjQ  hžhubh¢)”}”(hhh]”(h§)”}”(hŒ1. cache”h]”hŒ1. cache”…””}”(hjm  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjj  hžhhŸh¶h MUubh¸)”}”(hŒ‰The 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'cache' target.”h]”hŒ•The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜cacheâ€™ target.”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MVhjj  hžhubjf  )”}”(hXk  target_attributes := <target_name> "," <target_version> "," <metadata_mode> "," <cache_metadata_device> ","
                     <cache_device> "," <cache_origin_device> "," <writethrough> "," <writeback> ","
                     <passthrough> "," <no_discard_passdown> ";"

target_name := "target_name=cache"
target_version := "target_version=" <N> "." <N> "." <N>
metadata_mode := "metadata_mode=" <cache_metadata_mode>
cache_metadata_mode := "fail" | "ro" | "rw"
cache_device := "cache_device=" <cache_device_name_string>
cache_origin_device := "cache_origin_device=" <cache_origin_device_string>
writethrough := "writethrough=" <yes_no>
writeback := "writeback=" <yes_no>
passthrough := "passthrough=" <yes_no>
no_discard_passdown := "no_discard_passdown=" <yes_no>
yes_no := "y" | "n"

E.g.
When a 'cache' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'cache' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;name=cache1,uuid=cache_uuid,major=253,minor=2,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=28672,target_name=cache,target_version=2.2.0,metadata_mode=rw,
cache_metadata_device=253:4,cache_device=253:3,cache_origin_device=253:5,writethrough=y,writeback=n,
passthrough=n,metadata2=y,no_discard_passdown=n;”h]”hXk  target_attributes := <target_name> "," <target_version> "," <metadata_mode> "," <cache_metadata_device> ","
                     <cache_device> "," <cache_origin_device> "," <writethrough> "," <writeback> ","
                     <passthrough> "," <no_discard_passdown> ";"

target_name := "target_name=cache"
target_version := "target_version=" <N> "." <N> "." <N>
metadata_mode := "metadata_mode=" <cache_metadata_mode>
cache_metadata_mode := "fail" | "ro" | "rw"
cache_device := "cache_device=" <cache_device_name_string>
cache_origin_device := "cache_origin_device=" <cache_origin_device_string>
writethrough := "writethrough=" <yes_no>
writeback := "writeback=" <yes_no>
passthrough := "passthrough=" <yes_no>
no_discard_passdown := "no_discard_passdown=" <yes_no>
yes_no := "y" | "n"

E.g.
When a 'cache' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'cache' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;name=cache1,uuid=cache_uuid,major=253,minor=2,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=28672,target_name=cache,target_version=2.2.0,metadata_mode=rw,
cache_metadata_device=253:4,cache_device=253:3,cache_origin_device=253:5,writethrough=y,writeback=n,
passthrough=n,metadata2=y,no_discard_passdown=n;”…””}”hj‰  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M[hjj  hžhubeh}”(h]”Œcache”ah ]”h"]”Œ1. cache”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h MUubh¢)”}”(hhh]”(h§)”}”(hŒ2. crypt”h]”hŒ2. crypt”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjŸ  hžhhŸh¶h Mxubh¸)”}”(hŒ‰The 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'crypt' target.”h]”hŒ•The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜cryptâ€™ target.”…””}”(hj°  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MyhjŸ  hžhubjf  )”}”(hX  target_attributes := <target_name> "," <target_version> "," <allow_discards> "," <same_cpu_crypt> ","
                     <submit_from_crypt_cpus> "," <no_read_workqueue> "," <no_write_workqueue> ","
                     <iv_large_sectors> "," <iv_large_sectors> "," [<integrity_tag_size> ","] [<cipher_auth> ","]
                     [<sector_size> ","] [<cipher_string> ","] <key_size> "," <key_parts> ","
                     <key_extra_size> "," <key_mac_size> ";"

target_name := "target_name=crypt"
target_version := "target_version=" <N> "." <N> "." <N>
allow_discards := "allow_discards=" <yes_no>
same_cpu_crypt := "same_cpu_crypt=" <yes_no>
submit_from_crypt_cpus := "submit_from_crypt_cpus=" <yes_no>
no_read_workqueue := "no_read_workqueue=" <yes_no>
no_write_workqueue := "no_write_workqueue=" <yes_no>
iv_large_sectors := "iv_large_sectors=" <yes_no>
integrity_tag_size := "integrity_tag_size=" <N>
cipher_auth := "cipher_auth=" <string>
sector_size := "sector_size="  <N>
cipher_string := "cipher_string="
key_size := "key_size="  <N>
key_parts := "key_parts="  <N>
key_extra_size := "key_extra_size="  <N>
key_mac_size := "key_mac_size="  <N>
yes_no := "y" | "n"

E.g.
When a 'crypt' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'crypt' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=crypt1,uuid=crypt_uuid1,major=253,minor=0,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=1953125,target_name=crypt,target_version=1.23.0,
allow_discards=y,same_cpu=n,submit_from_crypt_cpus=n,no_read_workqueue=n,no_write_workqueue=n,
iv_large_sectors=n,cipher_string=aes-xts-plain64,key_size=32,key_parts=1,key_extra_size=0,key_mac_size=0;”h]”hX  target_attributes := <target_name> "," <target_version> "," <allow_discards> "," <same_cpu_crypt> ","
                     <submit_from_crypt_cpus> "," <no_read_workqueue> "," <no_write_workqueue> ","
                     <iv_large_sectors> "," <iv_large_sectors> "," [<integrity_tag_size> ","] [<cipher_auth> ","]
                     [<sector_size> ","] [<cipher_string> ","] <key_size> "," <key_parts> ","
                     <key_extra_size> "," <key_mac_size> ";"

target_name := "target_name=crypt"
target_version := "target_version=" <N> "." <N> "." <N>
allow_discards := "allow_discards=" <yes_no>
same_cpu_crypt := "same_cpu_crypt=" <yes_no>
submit_from_crypt_cpus := "submit_from_crypt_cpus=" <yes_no>
no_read_workqueue := "no_read_workqueue=" <yes_no>
no_write_workqueue := "no_write_workqueue=" <yes_no>
iv_large_sectors := "iv_large_sectors=" <yes_no>
integrity_tag_size := "integrity_tag_size=" <N>
cipher_auth := "cipher_auth=" <string>
sector_size := "sector_size="  <N>
cipher_string := "cipher_string="
key_size := "key_size="  <N>
key_parts := "key_parts="  <N>
key_extra_size := "key_extra_size="  <N>
key_mac_size := "key_mac_size="  <N>
yes_no := "y" | "n"

E.g.
When a 'crypt' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'crypt' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=crypt1,uuid=crypt_uuid1,major=253,minor=0,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=1953125,target_name=crypt,target_version=1.23.0,
allow_discards=y,same_cpu=n,submit_from_crypt_cpus=n,no_read_workqueue=n,no_write_workqueue=n,
iv_large_sectors=n,cipher_string=aes-xts-plain64,key_size=32,key_parts=1,key_extra_size=0,key_mac_size=0;”…””}”hj¾  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M~hjŸ  hžhubeh}”(h]”Œcrypt”ah ]”h"]”Œ2. crypt”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h Mxubh¢)”}”(hhh]”(h§)”}”(hŒ3. integrity”h]”hŒ3. integrity”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÔ  hžhhŸh¶h M£ubh¸)”}”(hŒThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'integrity' target.”h]”hŒ™The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜integrityâ€™ target.”…””}”(hjå  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M¤hjÔ  hžhubjf  )”}”(hX©  target_attributes := <target_name> "," <target_version> "," <dev_name> "," <start>
                     <tag_size> "," <mode> "," [<meta_device> ","] [<block_size> ","] <recalculate> ","
                     <allow_discards> "," <fix_padding> "," <fix_hmac> "," <legacy_recalculate> ","
                     <journal_sectors> "," <interleave_sectors> "," <buffer_sectors> ";"

target_name := "target_name=integrity"
target_version := "target_version=" <N> "." <N> "." <N>
dev_name := "dev_name=" <device_name_str>
start := "start=" <N>
tag_size := "tag_size=" <N>
mode := "mode=" <integrity_mode_str>
integrity_mode_str := "J" | "B" | "D" | "R"
meta_device := "meta_device=" <meta_device_str>
block_size := "block_size=" <N>
recalculate := "recalculate=" <yes_no>
allow_discards := "allow_discards=" <yes_no>
fix_padding := "fix_padding=" <yes_no>
fix_hmac := "fix_hmac=" <yes_no>
legacy_recalculate := "legacy_recalculate=" <yes_no>
journal_sectors := "journal_sectors=" <N>
interleave_sectors := "interleave_sectors=" <N>
buffer_sectors := "buffer_sectors=" <N>
yes_no := "y" | "n"

E.g.
When a 'integrity' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'integrity' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=integrity1,uuid=,major=253,minor=1,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=7856,target_name=integrity,target_version=1.10.0,
dev_name=253:0,start=0,tag_size=32,mode=J,recalculate=n,allow_discards=n,fix_padding=n,
fix_hmac=n,legacy_recalculate=n,journal_sectors=88,interleave_sectors=32768,buffer_sectors=128;”h]”hX©  target_attributes := <target_name> "," <target_version> "," <dev_name> "," <start>
                     <tag_size> "," <mode> "," [<meta_device> ","] [<block_size> ","] <recalculate> ","
                     <allow_discards> "," <fix_padding> "," <fix_hmac> "," <legacy_recalculate> ","
                     <journal_sectors> "," <interleave_sectors> "," <buffer_sectors> ";"

target_name := "target_name=integrity"
target_version := "target_version=" <N> "." <N> "." <N>
dev_name := "dev_name=" <device_name_str>
start := "start=" <N>
tag_size := "tag_size=" <N>
mode := "mode=" <integrity_mode_str>
integrity_mode_str := "J" | "B" | "D" | "R"
meta_device := "meta_device=" <meta_device_str>
block_size := "block_size=" <N>
recalculate := "recalculate=" <yes_no>
allow_discards := "allow_discards=" <yes_no>
fix_padding := "fix_padding=" <yes_no>
fix_hmac := "fix_hmac=" <yes_no>
legacy_recalculate := "legacy_recalculate=" <yes_no>
journal_sectors := "journal_sectors=" <N>
interleave_sectors := "interleave_sectors=" <N>
buffer_sectors := "buffer_sectors=" <N>
yes_no := "y" | "n"

E.g.
When a 'integrity' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'integrity' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=integrity1,uuid=,major=253,minor=1,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=7856,target_name=integrity,target_version=1.10.0,
dev_name=253:0,start=0,tag_size=32,mode=J,recalculate=n,allow_discards=n,fix_padding=n,
fix_hmac=n,legacy_recalculate=n,journal_sectors=88,interleave_sectors=32768,buffer_sectors=128;”…””}”hjó  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M©hjÔ  hžhubeh}”(h]”Œ	integrity”ah ]”h"]”Œ3. integrity”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h M£ubh¢)”}”(hhh]”(h§)”}”(hŒ	4. linear”h]”hŒ	4. linear”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj	  hžhhŸh¶h MÏubh¸)”}”(hŒŠThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'linear' target.”h]”hŒ–The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜linearâ€™ target.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÐhj	  hžhubjf  )”}”(hX×  target_attributes := <target_name> "," <target_version> "," <device_name> <,> <start> ";"

target_name := "target_name=linear"
target_version := "target_version=" <N> "." <N> "." <N>
device_name := "device_name=" <linear_device_name_str>
start := "start=" <N>

E.g.
When a 'linear' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'linear' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=linear1,uuid=linear_uuid1,major=253,minor=2,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=28672,target_name=linear,target_version=1.4.0,
device_name=253:1,start=2048;”h]”hX×  target_attributes := <target_name> "," <target_version> "," <device_name> <,> <start> ";"

target_name := "target_name=linear"
target_version := "target_version=" <N> "." <N> "." <N>
device_name := "device_name=" <linear_device_name_str>
start := "start=" <N>

E.g.
When a 'linear' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'linear' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=linear1,uuid=linear_uuid1,major=253,minor=2,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=28672,target_name=linear,target_version=1.4.0,
device_name=253:1,start=2048;”…””}”hj(  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h MÕhj	  hžhubeh}”(h]”Œlinear”ah ]”h"]”Œ	4. linear”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h MÏubh¢)”}”(hhh]”(h§)”}”(hŒ	5. mirror”h]”hŒ	5. mirror”…””}”(hjA  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj>  hžhhŸh¶h Mèubh¸)”}”(hŒŠThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'mirror' target.”h]”hŒ–The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜mirrorâ€™ target.”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Méhj>  hžhubjf  )”}”(hXÀ  target_attributes := <target_name> "," <target_version> "," <nr_mirrors> ","
                     <mirror_device_data> "," <handle_errors> "," <keep_log> "," <log_type_status> ";"

target_name := "target_name=mirror"
target_version := "target_version=" <N> "." <N> "." <N>
nr_mirrors := "nr_mirrors=" <NR>
mirror_device_data := <mirror_device_row> | <mirror_device_data><mirror_device_row>
                      mirror_device_row is repeated <NR> times - for <NR> described in <nr_mirrors>.
mirror_device_row := <mirror_device_name> "," <mirror_device_status>
mirror_device_name := "mirror_device_" <X> "=" <mirror_device_name_str>
                      where <X> ranges from 0 to (<NR> -1) - for <NR> described in <nr_mirrors>.
mirror_device_status := "mirror_device_" <X> "_status=" <mirror_device_status_char>
                        where <X> ranges from 0 to (<NR> -1) - for <NR> described in <nr_mirrors>.
mirror_device_status_char := "A" | "F" | "D" | "S" | "R" | "U"
handle_errors := "handle_errors=" <yes_no>
keep_log := "keep_log=" <yes_no>
log_type_status := "log_type_status=" <log_type_status_str>
yes_no := "y" | "n"

E.g.
When a 'mirror' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'mirror' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=mirror1,uuid=mirror_uuid1,major=253,minor=6,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=2048,target_name=mirror,target_version=1.14.0,nr_mirrors=2,
   mirror_device_0=253:4,mirror_device_0_status=A,
   mirror_device_1=253:5,mirror_device_1_status=A,
handle_errors=y,keep_log=n,log_type_status=;”h]”hXÀ  target_attributes := <target_name> "," <target_version> "," <nr_mirrors> ","
                     <mirror_device_data> "," <handle_errors> "," <keep_log> "," <log_type_status> ";"

target_name := "target_name=mirror"
target_version := "target_version=" <N> "." <N> "." <N>
nr_mirrors := "nr_mirrors=" <NR>
mirror_device_data := <mirror_device_row> | <mirror_device_data><mirror_device_row>
                      mirror_device_row is repeated <NR> times - for <NR> described in <nr_mirrors>.
mirror_device_row := <mirror_device_name> "," <mirror_device_status>
mirror_device_name := "mirror_device_" <X> "=" <mirror_device_name_str>
                      where <X> ranges from 0 to (<NR> -1) - for <NR> described in <nr_mirrors>.
mirror_device_status := "mirror_device_" <X> "_status=" <mirror_device_status_char>
                        where <X> ranges from 0 to (<NR> -1) - for <NR> described in <nr_mirrors>.
mirror_device_status_char := "A" | "F" | "D" | "S" | "R" | "U"
handle_errors := "handle_errors=" <yes_no>
keep_log := "keep_log=" <yes_no>
log_type_status := "log_type_status=" <log_type_status_str>
yes_no := "y" | "n"

E.g.
When a 'mirror' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'mirror' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=mirror1,uuid=mirror_uuid1,major=253,minor=6,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=2048,target_name=mirror,target_version=1.14.0,nr_mirrors=2,
   mirror_device_0=253:4,mirror_device_0_status=A,
   mirror_device_1=253:5,mirror_device_1_status=A,
handle_errors=y,keep_log=n,log_type_status=;”…””}”hj]  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h Mîhj>  hžhubeh}”(h]”Œmirror”ah ]”h"]”Œ	5. mirror”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h Mèubh¢)”}”(hhh]”(h§)”}”(hŒ6. multipath”h]”hŒ6. multipath”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjs  hžhhŸh¶h Mubh¸)”}”(hŒThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'multipath' target.”h]”hŒ™The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜multipathâ€™ target.”…””}”(hj„  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhjs  hžhubjf  )”}”(hXÒ  target_attributes := <target_name> "," <target_version> "," <nr_priority_groups>
                     ["," <pg_state> "," <priority_groups> "," <priority_group_paths>] ";"

target_name := "target_name=multipath"
target_version := "target_version=" <N> "." <N> "." <N>
nr_priority_groups := "nr_priority_groups=" <NPG>
priority_groups := <priority_groups_row>|<priority_groups_row><priority_groups>
priority_groups_row := "pg_state_" <X> "=" <pg_state_str> "," "nr_pgpaths_" <X>  "=" <NPGP> ","
                       "path_selector_name_" <X> "=" <string> "," <priority_group_paths>
                       where <X> ranges from 0 to (<NPG> -1) - for <NPG> described in <nr_priority_groups>.
pg_state_str := "E" | "A" | "D"
<priority_group_paths> := <priority_group_paths_row> | <priority_group_paths_row><priority_group_paths>
priority_group_paths_row := "path_name_" <X> "_" <Y> "=" <string> "," "is_active_" <X> "_" <Y> "=" <is_active_str>
                            "fail_count_" <X> "_" <Y> "=" <N> "," "path_selector_status_" <X> "_" <Y> "=" <path_selector_status_str>
                            where <X> ranges from 0 to (<NPG> -1) - for <NPG> described in <nr_priority_groups>,
                            and <Y> ranges from 0 to (<NPGP> -1) - for <NPGP> described in <priority_groups_row>.
is_active_str := "A" | "F"

E.g.
When a 'multipath' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'multipath' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=mp,uuid=,major=253,minor=0,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=2097152,target_name=multipath,target_version=1.14.0,nr_priority_groups=2,
   pg_state_0=E,nr_pgpaths_0=2,path_selector_name_0=queue-length,
       path_name_0_0=8:16,is_active_0_0=A,fail_count_0_0=0,path_selector_status_0_0=,
       path_name_0_1=8:32,is_active_0_1=A,fail_count_0_1=0,path_selector_status_0_1=,
   pg_state_1=E,nr_pgpaths_1=2,path_selector_name_1=queue-length,
       path_name_1_0=8:48,is_active_1_0=A,fail_count_1_0=0,path_selector_status_1_0=,
       path_name_1_1=8:64,is_active_1_1=A,fail_count_1_1=0,path_selector_status_1_1=;”h]”hXÒ  target_attributes := <target_name> "," <target_version> "," <nr_priority_groups>
                     ["," <pg_state> "," <priority_groups> "," <priority_group_paths>] ";"

target_name := "target_name=multipath"
target_version := "target_version=" <N> "." <N> "." <N>
nr_priority_groups := "nr_priority_groups=" <NPG>
priority_groups := <priority_groups_row>|<priority_groups_row><priority_groups>
priority_groups_row := "pg_state_" <X> "=" <pg_state_str> "," "nr_pgpaths_" <X>  "=" <NPGP> ","
                       "path_selector_name_" <X> "=" <string> "," <priority_group_paths>
                       where <X> ranges from 0 to (<NPG> -1) - for <NPG> described in <nr_priority_groups>.
pg_state_str := "E" | "A" | "D"
<priority_group_paths> := <priority_group_paths_row> | <priority_group_paths_row><priority_group_paths>
priority_group_paths_row := "path_name_" <X> "_" <Y> "=" <string> "," "is_active_" <X> "_" <Y> "=" <is_active_str>
                            "fail_count_" <X> "_" <Y> "=" <N> "," "path_selector_status_" <X> "_" <Y> "=" <path_selector_status_str>
                            where <X> ranges from 0 to (<NPG> -1) - for <NPG> described in <nr_priority_groups>,
                            and <Y> ranges from 0 to (<NPGP> -1) - for <NPGP> described in <priority_groups_row>.
is_active_str := "A" | "F"

E.g.
When a 'multipath' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'multipath' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=mp,uuid=,major=253,minor=0,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=2097152,target_name=multipath,target_version=1.14.0,nr_priority_groups=2,
   pg_state_0=E,nr_pgpaths_0=2,path_selector_name_0=queue-length,
       path_name_0_0=8:16,is_active_0_0=A,fail_count_0_0=0,path_selector_status_0_0=,
       path_name_0_1=8:32,is_active_0_1=A,fail_count_0_1=0,path_selector_status_0_1=,
   pg_state_1=E,nr_pgpaths_1=2,path_selector_name_1=queue-length,
       path_name_1_0=8:48,is_active_1_0=A,fail_count_1_0=0,path_selector_status_1_0=,
       path_name_1_1=8:64,is_active_1_1=A,fail_count_1_1=0,path_selector_status_1_1=;”…””}”hj’  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h Mhjs  hžhubeh}”(h]”Œ	multipath”ah ]”h"]”Œ6. multipath”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h Mubh¢)”}”(hhh]”(h§)”}”(hŒ7. raid”h]”hŒ7. raid”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj¨  hžhhŸh¶h M8ubh¸)”}”(hŒˆThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'raid' target.”h]”hŒ”The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜raidâ€™ target.”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M9hj¨  hžhubjf  )”}”(hXh  target_attributes := <target_name> "," <target_version> "," <raid_type> "," <raid_disks> "," <raid_state>
                     <raid_device_status> ["," journal_dev_mode] ";"

target_name := "target_name=raid"
target_version := "target_version=" <N> "." <N> "." <N>
raid_type := "raid_type=" <raid_type_str>
raid_disks := "raid_disks=" <NRD>
raid_state := "raid_state=" <raid_state_str>
raid_state_str := "frozen" | "reshape" |"resync" | "check" | "repair" | "recover" | "idle" |"undef"
raid_device_status := <raid_device_status_row> | <raid_device_status_row><raid_device_status>
                      <raid_device_status_row> is repeated <NRD> times - for <NRD> described in <raid_disks>.
raid_device_status_row := "raid_device_" <X> "_status=" <raid_device_status_str>
                          where <X> ranges from 0 to (<NRD> -1) - for <NRD> described in <raid_disks>.
raid_device_status_str := "A" | "D" | "a" | "-"
journal_dev_mode := "journal_dev_mode=" <journal_dev_mode_str>
journal_dev_mode_str := "writethrough" | "writeback" | "invalid"

E.g.
When a 'raid' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'raid' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=raid_LV1,uuid=uuid_raid_LV1,major=253,minor=12,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=2048,target_name=raid,target_version=1.15.1,
raid_type=raid10,raid_disks=4,raid_state=idle,
   raid_device_0_status=A,
   raid_device_1_status=A,
   raid_device_2_status=A,
   raid_device_3_status=A;”h]”hXh  target_attributes := <target_name> "," <target_version> "," <raid_type> "," <raid_disks> "," <raid_state>
                     <raid_device_status> ["," journal_dev_mode] ";"

target_name := "target_name=raid"
target_version := "target_version=" <N> "." <N> "." <N>
raid_type := "raid_type=" <raid_type_str>
raid_disks := "raid_disks=" <NRD>
raid_state := "raid_state=" <raid_state_str>
raid_state_str := "frozen" | "reshape" |"resync" | "check" | "repair" | "recover" | "idle" |"undef"
raid_device_status := <raid_device_status_row> | <raid_device_status_row><raid_device_status>
                      <raid_device_status_row> is repeated <NRD> times - for <NRD> described in <raid_disks>.
raid_device_status_row := "raid_device_" <X> "_status=" <raid_device_status_str>
                          where <X> ranges from 0 to (<NRD> -1) - for <NRD> described in <raid_disks>.
raid_device_status_str := "A" | "D" | "a" | "-"
journal_dev_mode := "journal_dev_mode=" <journal_dev_mode_str>
journal_dev_mode_str := "writethrough" | "writeback" | "invalid"

E.g.
When a 'raid' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'raid' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=raid_LV1,uuid=uuid_raid_LV1,major=253,minor=12,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=2048,target_name=raid,target_version=1.15.1,
raid_type=raid10,raid_disks=4,raid_state=idle,
   raid_device_0_status=A,
   raid_device_1_status=A,
   raid_device_2_status=A,
   raid_device_3_status=A;”…””•	7      }”hjÇ  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M>hj¨  hžhubeh}”(h]”Œraid”ah ]”h"]”Œ7. raid”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h M8ubh¢)”}”(hhh]”(h§)”}”(hŒ8. snapshot”h]”hŒ8. snapshot”…””}”(hjà  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÝ  hžhhŸh¶h M`ubh¸)”}”(hŒŒThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'snapshot' target.”h]”hŒ˜The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜snapshotâ€™ target.”…””}”(hjî  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MahjÝ  hžhubjf  )”}”(hX:  target_attributes := <target_name> "," <target_version> "," <snap_origin_name> ","
                     <snap_cow_name> "," <snap_valid> "," <snap_merge_failed> "," <snapshot_overflowed> ";"

target_name := "target_name=snapshot"
target_version := "target_version=" <N> "." <N> "." <N>
snap_origin_name := "snap_origin_name=" <string>
snap_cow_name := "snap_cow_name=" <string>
snap_valid := "snap_valid=" <yes_no>
snap_merge_failed := "snap_merge_failed=" <yes_no>
snapshot_overflowed := "snapshot_overflowed=" <yes_no>
yes_no := "y" | "n"

E.g.
When a 'snapshot' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'snapshot' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=snap1,uuid=snap_uuid1,major=253,minor=13,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=4096,target_name=snapshot,target_version=1.16.0,
snap_origin_name=253:11,snap_cow_name=253:12,snap_valid=y,snap_merge_failed=n,snapshot_overflowed=n;”h]”hX:  target_attributes := <target_name> "," <target_version> "," <snap_origin_name> ","
                     <snap_cow_name> "," <snap_valid> "," <snap_merge_failed> "," <snapshot_overflowed> ";"

target_name := "target_name=snapshot"
target_version := "target_version=" <N> "." <N> "." <N>
snap_origin_name := "snap_origin_name=" <string>
snap_cow_name := "snap_cow_name=" <string>
snap_valid := "snap_valid=" <yes_no>
snap_merge_failed := "snap_merge_failed=" <yes_no>
snapshot_overflowed := "snapshot_overflowed=" <yes_no>
yes_no := "y" | "n"

E.g.
When a 'snapshot' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'snapshot' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=snap1,uuid=snap_uuid1,major=253,minor=13,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=4096,target_name=snapshot,target_version=1.16.0,
snap_origin_name=253:11,snap_cow_name=253:12,snap_valid=y,snap_merge_failed=n,snapshot_overflowed=n;”…””}”hjü  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h MfhjÝ  hžhubeh}”(h]”Œsnapshot”ah ]”h"]”Œ8. snapshot”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h M`ubh¢)”}”(hhh]”(h§)”}”(hŒ
9. striped”h]”hŒ
9. striped”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h M~ubh¸)”}”(hŒ‹The 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'striped' target.”h]”hŒ—The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜stripedâ€™ target.”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj  hžhubjf  )”}”(hX   target_attributes := <target_name> "," <target_version> "," <stripes> "," <chunk_size> ","
                     <stripe_data> ";"

target_name := "target_name=striped"
target_version := "target_version=" <N> "." <N> "." <N>
stripes := "stripes=" <NS>
chunk_size := "chunk_size=" <N>
stripe_data := <stripe_data_row>|<stripe_data><stripe_data_row>
stripe_data_row := <stripe_device_name> "," <stripe_physical_start> "," <stripe_status>
stripe_device_name := "stripe_" <X> "_device_name=" <stripe_device_name_str>
                      where <X> ranges from 0 to (<NS> -1) - for <NS> described in <stripes>.
stripe_physical_start := "stripe_" <X> "_physical_start=" <N>
                          where <X> ranges from 0 to (<NS> -1) - for <NS> described in <stripes>.
stripe_status := "stripe_" <X> "_status=" <stripe_status_str>
                 where <X> ranges from 0 to (<NS> -1) - for <NS> described in <stripes>.
stripe_status_str := "D" | "A"

E.g.
When a 'striped' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'striped' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=striped1,uuid=striped_uuid1,major=253,minor=5,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=640,target_name=striped,target_version=1.6.0,stripes=2,chunk_size=64,
   stripe_0_device_name=253:0,stripe_0_physical_start=2048,stripe_0_status=A,
   stripe_1_device_name=253:3,stripe_1_physical_start=2048,stripe_1_status=A;”h]”hX   target_attributes := <target_name> "," <target_version> "," <stripes> "," <chunk_size> ","
                     <stripe_data> ";"

target_name := "target_name=striped"
target_version := "target_version=" <N> "." <N> "." <N>
stripes := "stripes=" <NS>
chunk_size := "chunk_size=" <N>
stripe_data := <stripe_data_row>|<stripe_data><stripe_data_row>
stripe_data_row := <stripe_device_name> "," <stripe_physical_start> "," <stripe_status>
stripe_device_name := "stripe_" <X> "_device_name=" <stripe_device_name_str>
                      where <X> ranges from 0 to (<NS> -1) - for <NS> described in <stripes>.
stripe_physical_start := "stripe_" <X> "_physical_start=" <N>
                          where <X> ranges from 0 to (<NS> -1) - for <NS> described in <stripes>.
stripe_status := "stripe_" <X> "_status=" <stripe_status_str>
                 where <X> ranges from 0 to (<NS> -1) - for <NS> described in <stripes>.
stripe_status_str := "D" | "A"

E.g.
When a 'striped' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'striped' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=striped1,uuid=striped_uuid1,major=253,minor=5,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=640,target_name=striped,target_version=1.6.0,stripes=2,chunk_size=64,
   stripe_0_device_name=253:0,stripe_0_physical_start=2048,stripe_0_status=A,
   stripe_1_device_name=253:3,stripe_1_physical_start=2048,stripe_1_status=A;”…””}”hj1  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M„hj  hžhubeh}”(h]”Œstriped”ah ]”h"]”Œ
9. striped”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h M~ubh¢)”}”(hhh]”(h§)”}”(hŒ
10. verity”h]”hŒ
10. verity”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjG  hžhhŸh¶h M¢ubh¸)”}”(hŒŠThe 'target_attributes' (described as part of EVENT_DATA in 'Table load'
section above) has the following data format for 'verity' target.”h]”hŒ–The â€˜target_attributesâ€™ (described as part of EVENT_DATA in â€˜Table loadâ€™
section above) has the following data format for â€˜verityâ€™ target.”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M£hjG  hžhubjf  )”}”(hX’  target_attributes := <target_name> "," <target_version> "," <hash_failed> "," <verity_version> ","
                     <data_device_name> "," <hash_device_name> "," <verity_algorithm> "," <root_digest> ","
                     <salt> "," <ignore_zero_blocks> "," <check_at_most_once> ["," <root_hash_sig_key_desc>]
                     ["," <verity_mode>] ";"

target_name := "target_name=verity"
target_version := "target_version=" <N> "." <N> "." <N>
hash_failed := "hash_failed=" <hash_failed_str>
hash_failed_str := "C" | "V"
verity_version := "verity_version=" <verity_version_str>
data_device_name := "data_device_name=" <data_device_name_str>
hash_device_name := "hash_device_name=" <hash_device_name_str>
verity_algorithm := "verity_algorithm=" <verity_algorithm_str>
root_digest := "root_digest=" <root_digest_str>
salt := "salt=" <salt_str>
salt_str := "-" <verity_salt_str>
ignore_zero_blocks := "ignore_zero_blocks=" <yes_no>
check_at_most_once := "check_at_most_once=" <yes_no>
root_hash_sig_key_desc := "root_hash_sig_key_desc="
verity_mode := "verity_mode=" <verity_mode_str>
verity_mode_str := "ignore_corruption" | "restart_on_corruption" | "panic_on_corruption" | "invalid"
yes_no := "y" | "n"

E.g.
When a 'verity' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'verity' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=test-verity,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=1953120,target_name=verity,target_version=1.8.0,hash_failed=V,
verity_version=1,data_device_name=253:1,hash_device_name=253:0,verity_algorithm=sha256,
root_digest=29cb87e60ce7b12b443ba6008266f3e41e93e403d7f298f8e3f316b29ff89c5e,
salt=e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d,
ignore_zero_blocks=n,check_at_most_once=n;”h]”hX’  target_attributes := <target_name> "," <target_version> "," <hash_failed> "," <verity_version> ","
                     <data_device_name> "," <hash_device_name> "," <verity_algorithm> "," <root_digest> ","
                     <salt> "," <ignore_zero_blocks> "," <check_at_most_once> ["," <root_hash_sig_key_desc>]
                     ["," <verity_mode>] ";"

target_name := "target_name=verity"
target_version := "target_version=" <N> "." <N> "." <N>
hash_failed := "hash_failed=" <hash_failed_str>
hash_failed_str := "C" | "V"
verity_version := "verity_version=" <verity_version_str>
data_device_name := "data_device_name=" <data_device_name_str>
hash_device_name := "hash_device_name=" <hash_device_name_str>
verity_algorithm := "verity_algorithm=" <verity_algorithm_str>
root_digest := "root_digest=" <root_digest_str>
salt := "salt=" <salt_str>
salt_str := "-" <verity_salt_str>
ignore_zero_blocks := "ignore_zero_blocks=" <yes_no>
check_at_most_once := "check_at_most_once=" <yes_no>
root_hash_sig_key_desc := "root_hash_sig_key_desc="
verity_mode := "verity_mode=" <verity_mode_str>
verity_mode_str := "ignore_corruption" | "restart_on_corruption" | "panic_on_corruption" | "invalid"
yes_no := "y" | "n"

E.g.
When a 'verity' target is loaded, then IMA ASCII measurement log will have an entry
similar to the following, depicting what 'verity' attributes are measured in EVENT_DATA
for 'dm_table_load' event.
(converted from ASCII to text for readability)

dm_version=4.45.0;
name=test-verity,uuid=,major=253,minor=2,minor_count=1,num_targets=1;
target_index=0,target_begin=0,target_len=1953120,target_name=verity,target_version=1.8.0,hash_failed=V,
verity_version=1,data_device_name=253:1,hash_device_name=253:0,verity_algorithm=sha256,
root_digest=29cb87e60ce7b12b443ba6008266f3e41e93e403d7f298f8e3f316b29ff89c5e,
salt=e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d,
ignore_zero_blocks=n,check_at_most_once=n;”…””}”hjf  sbah}”(h]”h ]”h"]”h$]”h&]”ju  jv  uh1je  hŸh¶h M¨hjG  hžhubeh}”(h]”Œverity”ah ]”h"]”Œ
10. verity”ah$]”h&]”uh1h¡hjQ  hžhhŸh¶h M¢ubeh}”(h]”Œsupported-targets”ah ]”h"]”Œsupported targets:”ah$]”h&]”uh1h¡hh£hžhhŸh¶h MEubeh}”(h]”Œdm-ima”ah ]”h"]”Œdm-ima”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j¯  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j‰  j†  jH  jE  jN  jK  j:  j7  j}  jz  jÀ  j½  j  j   jF  jC  j  j~  jœ  j™  jÑ  jÎ  j  j  j;  j8  jp  jm  j¥  j¢  jÚ  j×  j  j  jD  jA  jy  jv  uŒ	nametypes”}”(j‰  ‰jH  ‰jN  ‰j:  ‰j}  ‰jÀ  ‰j  ‰jF  ‰j  ‰jœ  ‰jÑ  ‰j  ‰j;  ‰jp  ‰j¥  ‰jÚ  ‰j  ‰jD  ‰jy  ‰uh}”(j†  h£jE  jF  jK  jK  j7  jú  jz  j=  j½  j€  j   jÃ  jC  j  j~  jQ  j™  jj  jÎ  jŸ  j  jÔ  j8  j	  jm  j>  j¢  js  j×  j¨  j  jÝ  jA  j  jv  jG  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.