linux-kernel - Re: [PATCH 00/14] target: Initial support for DIF Type1+Type3 emulation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Jan 2014 20:03:28 +0200
From:	sagi grimberg <sagig@...lanox.com>
To:	"Nicholas A. Bellinger" <nab@...erainc.com>,
	target-devel <target-devel@...r.kernel.org>
CC:	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Christoph Hellwig <hch@....de>, Hannes Reinecke <hare@...e.de>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Nicholas Bellinger <nab@...ux-iscsi.org>
Subject: Re: [PATCH 00/14] target: Initial support for DIF Type1+Type3 emulation

On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger <nab@...ux-iscsi.org>
>
> Hi MKP & SCSI folks,
>
> This series contains initial support for target mode DIF Type1+Type3
> emulation within target core, RAMDISK_MCP device backend, and tcm_loop
> fabric driver.
>
> DIF emulation is enabled via a new 'pi_prot_type' device attribute
> within configfs, which is set after initial device configuration and
> before target fabric LUN export occurs.
>
> The DIF read/write verify emulation has been made generic enough so
> it can be used by other backend drivers (eg: FILEIO), as well as
> DIF v2 in the near future.  Also note that the majority of the logic
> has been groked from existing scsi_debug.c code.
>
> The current plan is to enable basic support for emulated backends with
> tcm_loop for v3.14 code, and then move onto IBLOCK backend support
> (that requires BLOCK layer changes)

Hey Nic,
Can you please elaborate on what BLOCK layer changes are required?
I didn't spot any misses from Looking at 
Documentation/block/data-integrity.txt.

Am I missing something?

Sagi.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/