f75b6fae1a
Instead of providing DIF verify routines for read/write
that are almost identical and conditionally copy protection
information, just let the caller do the right thing.
Have a single sbc_dif_verify that handles an sgl (that
does NOT copy any data) and a protection information copy
routine used by rd_mcp and fileio backend.
In the WRITE case, call sbc_dif_verify with cmd->t_prot_sg
and then do the copy from it to local sgl (assuming the verify
succeeded of course). In the READ case, call sbc_dif_verify
with the local sgl and if it succeeds, copy it to t_prot_sg (or
not if we are stripping it).
(Fix apply breakage from commit
|
||
|---|---|---|
| .. | ||
| iscsi | ||
| configfs_macros.h | ||
| target_core_backend.h | ||
| target_core_backend_configfs.h | ||
| target_core_base.h | ||
| target_core_configfs.h | ||
| target_core_fabric.h | ||
| target_core_fabric_configfs.h | ||