From: Dave Chinner <david@fromorbit.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [REPOST, PATCH 0/3] dio: serialise unaligned direct IO
Date: Mon, 8 Nov 2010 18:40:20 +1100 [thread overview]
Message-ID: <1289202023-15102-1-git-send-email-david@fromorbit.com> (raw)
Repost of the last version of the series I wrote to prevent data corruption
cause by concurrent sub-block direct IO to the same block in the filesystem.
The problem still exists, the xfstest 240 is still triggering it, so we still
need to fix it.
next reply other threads:[~2010-11-08 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 7:40 Dave Chinner [this message]
2010-11-08 7:40 ` [PATCH 1/3] dio: track and serialise unaligned direct IO Dave Chinner
2010-11-08 15:28 ` Jeff Moyer
2010-11-08 22:55 ` Dave Chinner
2010-11-08 7:40 ` [PATCH 2/3] dio: scale unaligned IO tracking via multiple lists Dave Chinner
2010-11-08 15:36 ` Jeff Moyer
2010-11-08 23:12 ` Dave Chinner
2010-11-09 21:04 ` Jeff Moyer
2010-11-09 23:06 ` Dave Chinner
2010-11-11 15:32 ` Jeff Moyer
2010-11-08 7:40 ` [PATCH 3/3] dio: add a mempool for the unaligned block structures Dave Chinner
2010-11-08 15:40 ` Jeff Moyer
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=1289202023-15102-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).