From: Richard Curnow <Richard.Curnow@superh.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: struct nfs_fattr alignment problem in nfs3proc.c
Date: Fri, 21 Mar 2003 17:52:06 +0000 [thread overview]
Message-ID: <20030321175206.GA17163@malvern.uk.w2k.superh.com> (raw)
In the nfs3_proc_unlink_setup function, there appears to be a bug with
the way kmalloc is used to allocate storage for two structs grouped
together. The second struct ends up with a non 8-byte aligned pointer,
which can cause trouble later (in xdr_decode_fattr) when stores occur to
the u64 fields inside it. The following patch (on 2.4.19) fixes this
problem, though I'm not sure if it's the cleanest fix. (I hit this when
working on the port to SH-5, which is currently baselined on 2.4.19).
--- ../linux-2.4/fs/nfs/nfs3proc.c Fri Jan 3 15:01:17 2003
+++ fs/nfs/nfs3proc.c Fri Mar 21 17:42:38 2003
@@ -294,25 +294,28 @@
nfs_refresh_inode(dir, &dir_attr);
dprintk("NFS reply remove: %d\n", status);
return status;
}
static int
nfs3_proc_unlink_setup(struct rpc_message *msg, struct dentry *dir, struct qstr *name)
{
struct nfs3_diropargs *arg;
struct nfs_fattr *res;
+ int arg_size_8, res_size_8;
- arg = (struct nfs3_diropargs *)kmalloc(sizeof(*arg)+sizeof(*res), GFP_KERNEL);
+ arg_size_8 = (sizeof(*arg) + 7) & ~7;
+ res_size_8 = (sizeof(*res) + 7) & ~7;
+ arg = (struct nfs3_diropargs *)kmalloc(arg_size_8 + res_size_8, GFP_KERNEL);
if (!arg)
return -ENOMEM;
- res = (struct nfs_fattr*)(arg + 1);
+ res = (struct nfs_fattr*)((char *)arg + arg_size_8);
arg->fh = NFS_FH(dir->d_inode);
arg->name = name->name;
arg->len = name->len;
res->valid = 0;
msg->rpc_proc = NFS3PROC_REMOVE;
msg->rpc_argp = arg;
msg->rpc_resp = res;
return 0;
}
--
Richard \\\ SuperH Core+Debug Architect /// .. At home ..
P. /// richard.curnow@superh.com /// rc@rc0.org.uk
Curnow \\\ http://www.superh.com/ /// www.rc0.org.uk
next reply other threads:[~2003-03-21 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 17:52 Richard Curnow [this message]
2003-03-22 11:00 ` Trond Myklebust
2003-03-24 12:09 ` Richard Curnow
2003-03-24 13:49 ` Richard Curnow
2003-03-24 14:06 ` Trond Myklebust
2003-03-24 14:21 ` Richard Curnow
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=20030321175206.GA17163@malvern.uk.w2k.superh.com \
--to=richard.curnow@superh.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®