From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: v9fs-developer@lists.sourceforge.net, trond.myklebust@fys.uio.no,
Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 2] Invalidate_inode_pages2 changes.
Date: Tue, 29 Aug 2006 11:30:15 +1000 [thread overview]
Message-ID: <20060829111641.18391.patches@notabene> (raw)
Hi all,
I'm picking up on a conversation that was started in late March
this year, and which didn't get anywhere much.
See
http://lkml.org/lkml/2006/3/31/93
and following.
The issue is that it is possible for an NFS client to lose writes
if a particular race is lost - and this has been seen in real life.
The patch discussed in the above mentioned converstation made two
changes, one of which was completely right. The over was slightly wrong.
Having explored the issue in some depth I now see how it was wrong
and present below for your enjoyment two patches. One which makes
and justifies the first change. One which makes and justifies a
revised version of the second change.
Thanks,
NeilBrown
[PATCH 001 of 2] Invalidate_inode_pages2 shouldn't abort on first error.
[PATCH 002 of 2] Make data destruction in invalidate_inode_pages2 optional.
next reply other threads:[~2006-08-29 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 1:30 NeilBrown [this message]
2006-08-29 1:30 ` [PATCH 001 of 2] Invalidate_inode_pages2 shouldn't abort on first error NeilBrown
2006-08-29 1:30 ` [PATCH 002 of 2] Make data destruction in invalidate_inode_pages2 optional NeilBrown
2006-08-29 2:14 ` [PATCH 000 of 2] Invalidate_inode_pages2 changes Andrew Morton
2006-08-29 2:46 ` Neil Brown
2006-08-29 3:43 ` Andrew Morton
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=20060829111641.18391.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=v9fs-developer@lists.sourceforge.net \
/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®