summaryrefslogtreecommitdiffstats
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-05-01 22:20:58 -0700
commit056e8924a072d22007275dfb8b247bb814765b67 (patch)
tree896b93f5a9008de35ec780e83df907518cbc4ed5 /include/target
parentf11b55d13563e9428c88c873f4f03a6bef11ec0a (diff)
downloadlinux-stable-056e8924a072d22007275dfb8b247bb814765b67.tar.gz
linux-stable-056e8924a072d22007275dfb8b247bb814765b67.tar.bz2
linux-stable-056e8924a072d22007275dfb8b247bb814765b67.zip
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 ccfad0e9c2cd..0c1dce2ac6f0 100644
--- a/include/target/target_core_base.h
+++ b/include/target/target_core_base.h
@@ -664,6 +664,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;