From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC 3/3] GFS2 rename race - core changes
Date: Tue, 12 Dec 2006 03:19:05 -0500 [thread overview]
Message-ID: <457E65F9.50609@redhat.com> (raw)
Upon failure of gfs2_unlink_ok(), we discard the old dentry, create a
new dentry, and then fill in the correct inode contents. This is to
avoid gfs_rename() returns ENOENT for destination file changes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfs2_rename_core.patch
Type: text/x-patch
Size: 6257 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20061212/0dd5e077/attachment.bin>
next reply other threads:[~2006-12-12 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 8:19 Wendy Cheng [this message]
2006-12-12 9:13 ` [Cluster-devel] [RFC 3/3] GFS2 rename race - core changes Steven Whitehouse
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=457E65F9.50609@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.