summaryrefslogtreecommitdiff
path: root/include/target
diff options
context:
space:
mode:
authorDmitry Monakhov <dmonakhov@openvz.org>2017-03-31 19:53:36 +0400
committerNicholas Bellinger <nab@linux-iscsi.org>2017-04-02 16:36:39 -0700
commit9f7ebfc64d2c4716087e637c8924d4d9770944c1 (patch)
tree7407c3bc0ab606a9c96ac34cc2ef36a7bdbb9be1 /include/target
parent702b648106005de3f9f3fe2120b972230cab82c8 (diff)
downloadlinux-next-9f7ebfc64d2c4716087e637c8924d4d9770944c1.tar.gz
tcm: make pi data verification configurable
Currently ramdisk and fileio always perform PI verification before and after backend IO. This approach is not very flexible. Because some one may want to postpone this work to other layers in IO stack. For example if we want to test blk_integrity_profile testcase: https://github.com/dmonakhov/xfstests/commit/dee408c868861d6b6871dbb3381facee7effdbe4 Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org> Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'include/target')
-rw-r--r--include/target/target_core_base.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/target/target_core_base.h b/include/target/target_core_base.h
index 4b784b6e21c0..30877384ef69 100644
--- a/include/target/target_core_base.h
+++ b/include/target/target_core_base.h
@@ -667,6 +667,7 @@ struct se_dev_attrib {
int pi_prot_format;
enum target_prot_type pi_prot_type;
enum target_prot_type hw_pi_prot_type;
+ int pi_prot_verify;
int enforce_pr_isids;
int force_pr_aptpl;
int is_nonrot;