From: "Alan Miller" <pushingthecharacterlimit@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: dm-crypt: disabling barriers, data corruption
Date: Wed, 16 May 2007 13:03:45 -0500 [thread overview]
Message-ID: <feeb478c0705161103idf7b577t4e6011ec506f1747@mail.gmail.com> (raw)
Prior to 2.6.19, dm-crypt passes write barrier requests through to the
underlying device in the order received unmodified (the ordering).
In 2.6.19 and newer, these writes are now passed through a workqueue.
On an SMP box running encrpytion for write requests in parallel,
wouldn't this cause the requests to arrive to the device in a
different order? A 2.6.22 patch from Milan Broz sets dm-crypt to
disable barriers, but if this disabling is being handled at the
filesystem level, is there still a chance of data becoming corrupt?
I'm currently running an unpatched 2.6.20 kernel on an SMP machine
testing the validity of some static files going back and forth through
dm-crypt on an XFS filesystem mounted with nobarrier to be sure, and
so far I'm not noticing anything, but this is hardly a good test.
Suggestions or any other way to help out appreciated.
reply other threads:[~2007-05-16 18:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=feeb478c0705161103idf7b577t4e6011ec506f1747@mail.gmail.com \
--to=pushingthecharacterlimit@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®