From: bmarzins@sourceware.org <bmarzins@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs ops_inode.c
Date: 23 Oct 2006 20:47:24 -0000 [thread overview]
Message-ID: <20061023204724.28486.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: bmarzins at sourceware.org 2006-10-23 20:47:23
Modified files:
gfs-kernel/src/gfs: ops_inode.c
Log message:
Really gross hack!!!
This is a workaround for one of the bugs the got lumped into 166701. It
breaks POSIX behavior in a corner case to avoid crashing... It's icky.
when NFS opens a file with O_CREAT, the kernel nfs daemon checks to see
if the file exists. If it does, nfsd does the *right thing* (either opens the
file, or if the file was opened with O_EXCL, returns an error). If the file
doesn't exist, it passes the request down to the underlying file system.
Unfortunately, since nfs *knows* that the file doesn't exist, it doesn't
bother to pass a nameidata structure, which would include the intent
information. However since gfs is a cluster file system, the file could have
been created on another node after nfs checks for it. If this is the case,
gfs needs the intent information to do the *right thing*. It panics when
it finds a NULL pointer, instead of the nameidata. Now, instead of panicing,
if gfs finds a NULL nameidata pointer. It assumes that the file was not
created with O_EXCL.
This assumption could be wrong, with the result that an application could
thing that it has created a new file, when in fact, it has opened an existing
one.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_inode.c.diff?cvsroot=cluster&r1=1.14&r2=1.15
--- cluster/gfs-kernel/src/gfs/ops_inode.c 2006/10/15 07:25:09 1.14
+++ cluster/gfs-kernel/src/gfs/ops_inode.c 2006/10/23 20:47:23 1.15
@@ -118,7 +118,7 @@
if (!error)
break;
else if (error != -EEXIST ||
- (nd->intent.open.flags & O_EXCL)) {
+ (nd && (nd->intent.open.flags & O_EXCL))) {
gfs_holder_uninit(&d_gh);
return error;
}
next reply other threads:[~2006-10-23 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 20:47 bmarzins [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-11 22:15 [Cluster-devel] cluster/gfs-kernel/src/gfs ops_inode.c rpeterso
2007-07-11 21:58 rpeterso
2007-06-29 21:57 rpeterso
2007-06-05 18:21 wcheng
2007-06-05 17:46 wcheng
2007-01-18 20:40 wcheng
2006-10-15 7:25 wcheng
2006-10-03 17:27 rohara
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=20061023204724.28486.qmail@sourceware.org \
--to=bmarzins@sourceware.org \
/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.