On Fri, 2017-03-31 at 19:53 +0400, Dmitry Monakhov wrote: > 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@xxxxxxxxxx> > --- > drivers/target/target_core_configfs.c | 34 ++++++++++++++++++++++++++++++++++ > drivers/target/target_core_file.c | 6 ++++-- > drivers/target/target_core_rd.c | 17 +++++++++-------- > include/target/target_core_base.h | 1 + > 4 files changed, 48 insertions(+), 10 deletions(-) > Applied to target-pending/for-next. Btw, thanks for going the extra step to ensure existing behavior vs. the new pi_prot_verify attribute is retained. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
