linux-kernel - Re: [PATCH 5 of 7] block: Block/request layer data integrity support

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]

Message-ID: <20080608042754.GA21251@kroah.com>
Date:	Sat, 7 Jun 2008 21:27:54 -0700
From:	Greg KH <greg@...ah.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH 5 of 7] block: Block/request layer data integrity
	support

On Sat, Jun 07, 2008 at 12:55:38AM -0400, Martin K. Petersen wrote:
> +5.1 NORMAL FILESYSTEM
> +
> +    The normal filesystem is unaware that the underlying block device
> +    is capable of sending/receiving integrity metadata.  The IMD will
> +    be automatically generated by the block layer at submit_bio() time
> +    in case of a WRITE.  A READ request will cause the I/O integrity
> +    to be verified upon completion.
> +
> +    IMD generation and verification can be toggled using the
> +
> +      /sys/class/block/<bdev>/integrity/write_generate
> +
> +    and
> +
> +      /sys/class/block/<bdev>/integrity/read_verify
> +
> +    flags.
> +

All of the sysfs interfaces should be documented in Documentation/ABI/
not here, otherwise they will be tough to find and figure out how to
use :)

thanks,

greg k-h
--
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/