From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Jiri Palecek <jpalecek@web.de>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Fix cleanup procedure in the setuid04 test
Date: Thu, 25 Jun 2009 14:40:24 +0530 [thread overview]
Message-ID: <1245921024.5542.42.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <op.uvzv3omsu2flwt@debian>
On Tue, 2009-06-23 at 22:48 +0200, Jiří Paleček wrote:
> On Tue, 23 Jun 2009 17:41:15 +0200, Jiří Paleček <jpalecek@web.de> wrote:
>
> > On Tue, 23 Jun 2009 16:49:03 +0200, Subrata Modak
> > <subrata@linux.vnet.ibm.com> wrote:
> >
> >> On Tue, 2009-05-12 at 19:06 +0200, Jiri Palecek wrote:
> >>> Cleanup has to be made only once in the parent process; when the
> >>> child makes the cleanup itself, the parent has nothing to cleanup,
> >>> which makes him sad.
> >>>
> >>> Signed-off-by: Jiri Palecek <jpalecek@web.de>
> >>
> >> Thanks.
> >
> > Oh no, at the second sight I see I've posted a wrong (old) version of
> > the patch. I'll send a correction shortly.
>
> The correction is in the attachment. Please, apply.
Everythings fine except:
(Stripping trailing CRs from patch.)
patching file testcases/kernel/syscalls/setuid/setuid04.c
Regards--
Subrata
>
> Regards
> Jiri Palecek
>
> >>> ---
> >>> testcases/kernel/syscalls/setuid/setuid04.c | 7 +++----
> >>> 1 files changed, 3 insertions(+), 4 deletions(-)
> >>>
> >>> diff --git a/testcases/kernel/syscalls/setuid/setuid04.c
> >>> b/testcases/kernel/syscalls/setuid/setuid04.c
> >>> index 18f1d90..26a3868 100644
> >>> --- a/testcases/kernel/syscalls/setuid/setuid04.c
> >>> +++ b/testcases/kernel/syscalls/setuid/setuid04.c
> >>> @@ -114,7 +114,7 @@ void do_master_child()
> >>> int status;
> >>>
> >>> if (setuid(ltpuser->pw_uid) == -1) {
> >>> - tst_brkm(TBROK, cleanup,
> >>> + tst_brkm(TBROK, tst_exit,
> >>> "setuid failed to set the effective uid to %d",
> >>> ltpuser->pw_uid);
> >>> }
> >>> @@ -143,7 +143,7 @@ void do_master_child()
> >>>
> >>> pid = FORK_OR_VFORK();
> >>> if (pid < 0)
> >>> - tst_brkm(TBROK, cleanup, "Fork failed");
> >>> + tst_brkm(TBROK, tst_exit, "Fork failed");
> >>>
> >>> if (pid == 0) {
> >>> int tst_fd2;
> >>> @@ -160,13 +160,12 @@ void do_master_child()
> >>>
> >>> if (TEST_ERRNO == EACCES) {
> >>> tst_resm(TPASS, "open returned errno EACCES");
> >>> - exit(0);
> >>> } else {
> >>> tst_resm(TFAIL,
> >>> "open returned unexpected errno - %d",
> >>> TEST_ERRNO);
> >>> - exit(-1);
> >>> }
> >>> + tst_exit();
> >>> } else {
> >>> /* Wait for son completion */
> >>> waitpid(pid, &status, 0);
> >>
> >
> >
> >
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-25 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906220117.n5M1HTVJ004183@e2.ny.us.ibm.com>
2009-06-23 14:49 ` [LTP] [PATCH] Fix cleanup procedure in the setuid04 test Subrata Modak
2009-06-23 15:41 ` Jiří Paleček
2009-06-23 20:48 ` Jiří Paleček
2009-06-25 9:10 ` Subrata Modak [this message]
2009-05-12 17:06 Jiri Palecek
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=1245921024.5542.42.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=jpalecek@web.de \
--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