From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] ltp: fix typo in testcases/kernel/syscalls/chown/chown03.c
Date: Wed, 27 May 2009 11:43:03 +0800 [thread overview]
Message-ID: <4A1CB6C7.6070302@cn.fujitsu.com> (raw)
Fix typo in testcases/kernel/syscalls/chown/chown03.c,
which use ltpuser->pw_uid in call to setegid() should
be ltpuser->pw_gid.
Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
---
testcases/kernel/syscalls/chown/chown03.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/syscalls/chown/chown03.c b/testcases/kernel/syscalls/chown/chown03.c
index fde107a..f27cb6f 100644
--- a/testcases/kernel/syscalls/chown/chown03.c
+++ b/testcases/kernel/syscalls/chown/chown03.c
@@ -213,9 +213,9 @@ void setup()
}
ltpuser = getpwnam(nobody_uid);
- if (setegid(ltpuser->pw_uid) == -1) {
+ if (setegid(ltpuser->pw_gid) == -1) {
tst_resm(TINFO, "setegid failed to "
- "to set the effective uid to %d", ltpuser->pw_uid);
+ "to set the effective uid to %d", ltpuser->pw_gid);
perror("setegid");
}
if (seteuid(ltpuser->pw_uid) == -1) {
--
1.6.0.2.530.g67faa
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-05-27 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 3:43 Wei Yongjun [this message]
2009-05-27 14:23 ` [LTP] [PATCH] ltp: fix typo in testcases/kernel/syscalls/chown/chown03.c Subrata Modak
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=4A1CB6C7.6070302@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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