linux-ext4 - Re: [PATCH 0 of 7] Block/SCSI 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-next>] [day] [month] [year] [list]

Date:	Thu, 17 Jul 2008 09:55:45 -0400
From:	"Mike Snitzer" <snitzer@...il.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
Cc:	"Jeff Moyer" <jmoyer@...hat.com>, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0 of 7] Block/SCSI Data Integrity Support

On Tue, Jun 10, 2008 at 11:28 AM, Martin K. Petersen
<martin.petersen@...cle.com> wrote:
>>>>>> "Jeff" == Jeff Moyer <jmoyer@...hat.com> writes:
>
> Jeff> Thanks for all of the great documentation.  It would be good to
> Jeff> include some instructions on how one would test this, and what
> Jeff> testing you performed.
>
> modprobe scsi_debug dix=199 dif=1 guard=1 dev_size_mb=1024 num_parts=1
>
> I'm testing with XFS and btrfs.  Generally doing kernel builds, etc.
> ext2/3 are still problematic because they modify pages in flight.

Have you made the ext2/3/4 developers aware of this?

Could you elaborate on the interaction between the data integrity
support in the block layer and a given filesystem?  Shouldn't _any_
filesystem "just work" given that the block layer is what is
generating the checksums and then verifying them on read?

regards,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html