From: faizan husain <faizanh@linux.vnet.ibm.com>
To: linux-nfs@vger.kernel.org
Cc: Frank S Filz <ffilz@us.ibm.com>, jvrao@linux.vnet.ibm.com
Subject: [PATCH] nfs4-acl-tools : nfs4_setfacl' failed with unexpected messages if the format of the input file is incorrect.
Date: Wed, 29 Jun 2011 12:51:28 +0530 [thread overview]
Message-ID: <4E0AD278.3000503@linux.vnet.ibm.com> (raw)
On RHEL5.5 and above releases,
read ACL entries to set from file leads to a segmentation fault on pp64,
more over the same problem does not show up for x86_64 architecture.
here is what i tried.
mounted a file system over nfs4.
#rpm -qa | grep nfs4
nfs4-acl-tools-0.3.3-5.el6.ppc64
'nfs4_setfacl' failed with unexpected message:
#nfs4_setfacl -S file4 file1
*** glibc detected *** nfs4_setfacl: double free or corruption (out):
0x08007760 ***
expected out should be like
Scanning ACE string 'abcd' failed.
Failed while inserting ACE(s).
From b8333732964780394518be74ab0b7c61a7e4be4f Mon Sep 17 00:00:00 2001
From: faizan <faizan.husain@xxxxxxx>
Date: Tue, 28 Jun 2011 16:06:47 +0530
Subject: [PATCH][BUILD]] FIX - 'nfs4_setfacl' failed with unexpected
messages iff
the format of the input file is incorrect.
Signed-off-by: faizan <faizan.husain@xxxxxxxx>
---
libnfs4acl/nfs4_ace_from_string.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/libnfs4acl/nfs4_ace_from_string.c
b/libnfs4acl/nfs4_ace_from_string.c
index 9d877fb..1cc220e 100644
--- a/libnfs4acl/nfs4_ace_from_string.c
+++ b/libnfs4acl/nfs4_ace_from_string.c
@@ -125,7 +125,6 @@ parse_alloc_fields(char *buf, char *fields[NUMFIELDS])
return 0;
out_free:
- free_fields(fields);
return -ENOMEM;
}
--
1.7.1
Regards
Faizan
next reply other threads:[~2011-06-29 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 7:21 faizan husain [this message]
2011-06-29 12:18 ` [PATCH] nfs4-acl-tools : nfs4_setfacl' failed with unexpected messages if the format of the input file is incorrect Jim Rees
2011-06-30 6:07 ` faizan husain
2011-06-30 11:51 ` Jim Rees
2011-06-30 13:33 ` faizan husain
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=4E0AD278.3000503@linux.vnet.ibm.com \
--to=faizanh@linux.vnet.ibm.com \
--cc=ffilz@us.ibm.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=linux-nfs@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.