From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC 0/3] GFS2 rename race
Date: Wed, 13 Dec 2006 01:01:32 -0500 [thread overview]
Message-ID: <457F973C.9030206@redhat.com> (raw)
In-Reply-To: <1165969852.20600.20.camel@xenon.msp.redhat.com>
Russell Cattelan wrote:
>I applied the three patches
>
>Putz-Less Yum Nut->quilt applied (fix it fool)?yes
>gfs2_refresh_inode.patch
>gfs2_rename_lock.patch
>gfs2_rename_core.patch
>
>s/built-in.o: In function `gfs2_get_dentry':
>/fs/gfs2/ops_export.c:294: undefined reference to `gfs2_refresh_inode'
>
>
>Did I miss something?
>
>
>
No, you didn't. The patches were ported from GFS1 (which were quite
messy when compared with GFS2). I manually made GFS2 patches one by one
(for review purpose). Then I made some function name changes in the
overall kernel source while doing the final round of testings.
Apparently I forgot to go back to fix the first patch. The
gfs2_refresh_inode should have been "gfs2_refresh_iobj". Will submit the
fixed patch set after I've done with Steve's suggestion (on patch #3).
Thanks for catching this.
-- Wendy
prev parent reply other threads:[~2006-12-13 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 7:53 [Cluster-devel] [RFC 0/3] GFS2 rename race Wendy Cheng
2006-12-13 0:30 ` Russell Cattelan
2006-12-13 6:01 ` Wendy Cheng [this message]
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=457F973C.9030206@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.