From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC 1/3] GFS2 rename race - refresh inode
Date: Tue, 12 Dec 2006 03:01:48 -0500 [thread overview]
Message-ID: <457E61EC.8030605@redhat.com> (raw)
This patch yanks inode refresh logic out of gfs2_get_dentry() (currently
used by NFS serving) so rename and NFS can share the same logic. It may
look big but actually doesn't change any logic.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2_refresh_inode.patch
Type: text/x-patch
Size: 2761 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20061212/37eb2465/attachment.bin>
reply other threads:[~2006-12-12 8:01 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=457E61EC.8030605@redhat.com \
--to=wcheng@redhat.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.