linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Mikulas Patocka <mpatocka@redhat.com>, Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [dm-devel] Some thoughts about providing data block checksumming for ext4
Date: Wed, 05 Nov 2014 22:37:09 +0100	[thread overview]
Message-ID: <545A9885.8070901@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1411041915430.32105@file01.intranet.prod.int.rdu2.redhat.com>

On 11/05/2014 01:27 AM, Mikulas Patocka wrote:

> So you really need cryptographic hashes instead of checksums to avoid the 
> collisions.

I am not sure if it was mentioned but also see how integrity is implemented in
FreeBSD GELI system by playing with sector sizes
 
http://svnweb.freebsd.org/base/head/sys/geom/eli/g_eli_integrity.c?view=co

Also, for encrypted devices (either on file level or block level) I think 
there are still requests for implementing real crypto authenticated modes (like GCM)
which obviously need similar space for auth tag. (I think ZFS uses it this way.) 

Milan


  reply	other threads:[~2014-11-05 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 23:33 Some thoughts about providing data block checksumming for ext4 Theodore Ts'o
2014-11-04 21:20 ` Andreas Dilger
2014-11-04 23:58   ` Theodore Ts'o
2014-11-04 21:39 ` [dm-devel] " Mikulas Patocka
2014-11-04 22:06   ` Mikulas Patocka
2014-11-05  0:27     ` Mikulas Patocka
2014-11-05 21:37       ` Milan Broz [this message]
2014-11-06 12:55         ` Theodore Ts'o
2014-11-05  2:33   ` Theodore Ts'o
2014-11-26 23:47 ` Darrick J. Wong
2014-11-27  0:07   ` Mike Snitzer
2014-11-27  0:39     ` Darrick J. Wong
2015-01-23 16:46       ` [dm-devel] " Vasily Tarasov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=545A9885.8070901@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).