From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2: anti stale inode for nfs (for 1.4git)
Date: Thu, 03 Dec 2009 19:05:53 +0800 [thread overview]
Message-ID: <4B179B91.9020405@oracle.com> (raw)
Hi Joel,
I am talking about
http://oss.oracle.com/pipermail/ocfs2-devel/2009-March/004121.html
One customer hits the problem(ocfs2+nfs) --bug 9177818.
and I noticed that patch is not in 1.4 src yet.
I suggested ct to test the patch.
while, no reproduction doesn't mean the patch is good(condition not hit).
so if no reproduction, do we commit the patch to 1.4 src repos?
regards,
wengang.
--
--just begin to learn, you are never too late...
reply other threads:[~2009-12-03 11:05 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=4B179B91.9020405@oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.