diff options
author | Sagi Grimberg <sagig@mellanox.com> | 2015-04-19 20:27:19 +0300 |
---|---|---|
committer | Nicholas Bellinger <nab@linux-iscsi.org> | 2015-05-30 22:41:41 -0700 |
commit | f75b6fae1a1d0a79dcbb9cbaed1d06bf3fe57a3c (patch) | |
tree | b255e230aa10d9ad6a5e6d9944d7f82eb78bf662 /arch/avr32 | |
parent | b2feda4feb1b0ea74c0916b4a35b038bbfef9c82 (diff) | |
download | op-kernel-dev-f75b6fae1a1d0a79dcbb9cbaed1d06bf3fe57a3c.zip op-kernel-dev-f75b6fae1a1d0a79dcbb9cbaed1d06bf3fe57a3c.tar.gz |
target: Merge sbc_verify_dif_read|write
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 c836777 - nab)
Tested-by: Akinobu Mita <akinobu.mita@gmail.com>
Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'arch/avr32')
0 files changed, 0 insertions, 0 deletions