linux-kernel - Re: [PATCH 0 of 3] Block Layer Data Integrity

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] [day] [month] [year] [list]

Date:	Tue, 17 Jun 2008 18:57:02 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH 0 of 3] Block Layer Data Integrity

On Tue, Jun 17 2008, Martin K. Petersen wrote:
> 
> These patches allow data integrity information (checksum and more) to
> be attached to I/Os at the block/filesystem layers and transferred
> through the entire I/O stack all the way to the physical storage
> device.
> 
> The integrity metadata can be generated in close proximity to the
> original data.  Capable host adapters, RAID arrays and physical disks
> can verify the data integrity and abort I/Os in case of a mismatch.
> 
> Changes:
> 
>  - Add "if in doubt" to Kconfig
> 
>  - Make blk_rq_count_integrity_sg() more readable
> 
>  - Queue integrity sysfs fixes
> 
>  - Fix two struct bi leaks
> 
>  - Rename struct bip to bio_integrity_payload
> 
>  - Introduce bio_integrity_hw_sectors() that converts from block layer
>    (512b) sectors to hardware sectors
> 
>  - Fix kunmap_atomic() abuse
> 
>  - Replace ?: constructs with if()
> 
>  - Add __GFP_NOFAIL to bio_integrity_prep() allocation

Thanks Martin, looks good to me now. Applied to pending 2.6.27 queue.

-- 
Jens Axboe

--
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/