From: Vincent Hanquez <tab@snarc.org>
To: Darren Williams <dsw@gelato.unsw.edu.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
dhowells@redhat.com, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] 2.6.8-rc1 fix AFS struct_cpy use which break !X86
Date: Wed, 14 Jul 2004 03:21:10 +0200 [thread overview]
Message-ID: <20040714012110.GA5400@snarc.org> (raw)
In-Reply-To: <20040714010706.GA31683@cse.unsw.EDU.AU>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
On Wed, Jul 14, 2004 at 11:07:06AM +1000, Darren Williams wrote:
> Including Andrew File System on any arch other
> than i386 and x86_64 will break the compilation
> due to the use of 'struct_cpy()', which is only
> define in the two archs above and both archs
> define it differently:
struct_cpy will be remove as suggest by AKPM in a recent discussion in LKML.
> A quick discussion here suggests that we are not
> doing a deep copy of the struct though others
> may by able to enlighten us on what happens to
> pointers within a struct?
using only *x = *y works.
> I have applied the i386 definition to ia64 and
> compiles OK, though I cannot test it since I
> do not have direct access to AFS.
Ok, what about the following patch ?
Index: fs/afs/mntpt.c
===================================================================
--- fs/afs/mntpt.c (revision 1)
+++ fs/afs/mntpt.c (working copy)
@@ -257,7 +257,7 @@
if (IS_ERR(newmnt))
return PTR_ERR(newmnt);
- struct_cpy(&newnd, nd);
+ newnd = *nd;
newnd.dentry = dentry;
err = do_add_mount(newmnt, &newnd, 0, &afs_vfsmounts);
Index: fs/afs/vlocation.c
===================================================================
--- fs/afs/vlocation.c (revision 1)
+++ fs/afs/vlocation.c (working copy)
@@ -906,7 +906,7 @@
if (!vlocation->valid ||
vlocation->vldb.rtime == vldb->rtime
) {
- struct_cpy(&vlocation->vldb, vldb);
+ vlocation->vldb = *vldb;
vlocation->valid = 1;
_leave(" = SUCCESS [c->m]");
return CACHEFS_MATCH_SUCCESS;
@@ -947,7 +947,7 @@
_enter("");
- struct_cpy(vldb,&vlocation->vldb);
+ *vldb = vlocation->vldb;
} /* end afs_vlocation_cache_update() */
#endif
--
Tab
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-14 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 1:07 [PATCH] 2.6.8-rc1 including AFS in ia64 and other ARCHS builds breaks the compilation Darren Williams
2004-07-14 1:07 ` Darren Williams
2004-07-14 1:21 ` Vincent Hanquez [this message]
2004-07-14 2:19 ` [PATCH] 2.6.8-rc1 fix AFS struct_cpy use which break !X86 Darren Williams
2004-07-14 7:54 ` [PATCH] 2.6.8-rc1 including AFS in ia64 and other ARCHS builds breaks the compilation David Howells
2004-07-14 7:54 ` David Howells
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=20040714012110.GA5400@snarc.org \
--to=tab@snarc.org \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=dsw@gelato.unsw.edu.au \
--cc=linux-kernel@vger.kernel.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.