From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Paul Millar <paul.millar@desy.de>
Cc: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: A couple of questions
Date: Tue, 01 Jun 2010 09:39:52 -0400 [thread overview]
Message-ID: <yq1ljaykh1z.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <201005312006.47321.paul.millar@desy.de> (Paul Millar's message of "Mon, 31 May 2010 20:06:45 +0200")
>>>>> "Paul" == Paul Millar <paul.millar@desy.de> writes:
Paul> My concern is that, if the server-software doesn't push the
Paul> client-provided checksum then the FS checksum (plus T-10 DIF/DIX)
Paul> would not provide a rigorous assurance that the bytes are the
Paul> same. Without this assurance, corruption could still occur; for
Paul> example, within the server's memory.
For DIX we allow integrity metadata conversion. Once the data is
received, the server generates appropriate IMD for the next layer. Then
the server verifies that the original IMD matches the data buffer. That
way there's no window of error. But obviously the ideal case is where
the same IMD can be passed throughout the stack without conversion.
Not sure what you use for file service? I believe NFSv4 allows for
checksums to be passed along. I have not looked at them closely yet,
though.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2010-06-01 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 13:39 A couple of questions Paul Millar
2010-05-27 14:56 ` Hubert Kario
2010-05-31 17:59 ` Paul Millar
2010-06-02 16:19 ` Hubert Kario
2010-05-27 16:00 ` Chris Mason
2010-05-31 18:06 ` Paul Millar
2010-05-31 20:33 ` Mike Fedyk
2010-06-02 11:56 ` Paul Millar
2010-06-01 13:39 ` Martin K. Petersen [this message]
2010-06-02 13:40 ` Paul Millar
2010-06-04 1:17 ` Martin K. Petersen
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=yq1ljaykh1z.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=paul.millar@desy.de \
/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).