From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: aelder@sgi.com
Subject: [GIT PULL] xfs: unaligned AIO DIO corruption fixes
Date: Wed, 12 Jan 2011 11:45:11 +1100 [thread overview]
Message-ID: <20110112004511.GM28803@dastard> (raw)
Hi Alex,
The reviewed series is ready to be pulled into the master XFS
branch. Thanks.
The following changes since commit d0eb2f38b250b7d6c993adf81b0e4ded0565497e:
xfs: convert grant head manipulations to lockless algorithm (2010-12-21 12:29:14 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git xfs-for-2.6.38
Dave Chinner (8):
xfs: ensure sync write errors are returned
xfs: factor common post-write isize handling code
xfs: factor post-write newsize updates
xfs: introduce xfs_rw_lock() helpers for locking the inode
xfs: split direct IO write path from xfs_file_aio_write
xfs: split buffered IO write path from xfs_file_aio_write
xfs: factor common write setup code
xfs: serialise unaligned direct IOs
fs/xfs/linux-2.6/xfs_file.c | 535 +++++++++++++++++++++++++------------------
1 files changed, 307 insertions(+), 228 deletions(-)
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-01-12 0:44 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=20110112004511.GM28803@dastard \
--to=david@fromorbit.com \
--cc=aelder@sgi.com \
--cc=xfs@oss.sgi.com \
/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