60a89a3ce0
Commitddd0bc7569("block: move ref_tag calculation func to the block layer") moved ref tag calculation from SCSI to a library function. However, this change broke returning the correct ref tag for devices operating in DIF mode since these do not have an associated block integrity profile. This in turn caused read/write failures on PI-formatted disks attached to an mpt3sas controller. Fixes:ddd0bc7569("block: move ref_tag calculation func to the block layer") Cc: stable@vger.kernel.org # 4.19+ Reported-by: John Garry <john.garry@huawei.com> Tested-by: Xiang Chen <chenxiang66@hisilicon.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
71 lines
1.9 KiB
C
71 lines
1.9 KiB
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
#ifndef _LINUX_T10_PI_H
|
|
#define _LINUX_T10_PI_H
|
|
|
|
#include <linux/types.h>
|
|
#include <linux/blkdev.h>
|
|
|
|
/*
|
|
* A T10 PI-capable target device can be formatted with different
|
|
* protection schemes. Currently 0 through 3 are defined:
|
|
*
|
|
* Type 0 is regular (unprotected) I/O
|
|
*
|
|
* Type 1 defines the contents of the guard and reference tags
|
|
*
|
|
* Type 2 defines the contents of the guard and reference tags and
|
|
* uses 32-byte commands to seed the latter
|
|
*
|
|
* Type 3 defines the contents of the guard tag only
|
|
*/
|
|
enum t10_dif_type {
|
|
T10_PI_TYPE0_PROTECTION = 0x0,
|
|
T10_PI_TYPE1_PROTECTION = 0x1,
|
|
T10_PI_TYPE2_PROTECTION = 0x2,
|
|
T10_PI_TYPE3_PROTECTION = 0x3,
|
|
};
|
|
|
|
/*
|
|
* T10 Protection Information tuple.
|
|
*/
|
|
struct t10_pi_tuple {
|
|
__be16 guard_tag; /* Checksum */
|
|
__be16 app_tag; /* Opaque storage */
|
|
__be32 ref_tag; /* Target LBA or indirect LBA */
|
|
};
|
|
|
|
#define T10_PI_APP_ESCAPE cpu_to_be16(0xffff)
|
|
#define T10_PI_REF_ESCAPE cpu_to_be32(0xffffffff)
|
|
|
|
static inline u32 t10_pi_ref_tag(struct request *rq)
|
|
{
|
|
unsigned int shift = ilog2(queue_logical_block_size(rq->q));
|
|
|
|
#ifdef CONFIG_BLK_DEV_INTEGRITY
|
|
if (rq->q->integrity.interval_exp)
|
|
shift = rq->q->integrity.interval_exp;
|
|
#endif
|
|
return blk_rq_pos(rq) >> (shift - SECTOR_SHIFT) & 0xffffffff;
|
|
}
|
|
|
|
extern const struct blk_integrity_profile t10_pi_type1_crc;
|
|
extern const struct blk_integrity_profile t10_pi_type1_ip;
|
|
extern const struct blk_integrity_profile t10_pi_type3_crc;
|
|
extern const struct blk_integrity_profile t10_pi_type3_ip;
|
|
|
|
#ifdef CONFIG_BLK_DEV_INTEGRITY
|
|
extern void t10_pi_prepare(struct request *rq, u8 protection_type);
|
|
extern void t10_pi_complete(struct request *rq, u8 protection_type,
|
|
unsigned int intervals);
|
|
#else
|
|
static inline void t10_pi_complete(struct request *rq, u8 protection_type,
|
|
unsigned int intervals)
|
|
{
|
|
}
|
|
static inline void t10_pi_prepare(struct request *rq, u8 protection_type)
|
|
{
|
|
}
|
|
#endif
|
|
|
|
#endif
|