public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Jiri Palecek <jpalecek@web.de>
Cc: ltp-list@lists.sourceforge.net, Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [LTP] [PATCH] Run the eventfd test in a temporary directory, because it creates some files
Date: Tue, 30 Jun 2009 13:11:07 +0530	[thread overview]
Message-ID: <1246347667.4819.27.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <1245920973.5542.33.camel@subratamodak.linux.ibm.com>

Jiri,

On Thu, 2009-06-25 at 14:39 +0530, Subrata Modak wrote: 
> On Mon, 2008-12-29 at 14:48 +0100, Jiri Palecek wrote: 
> > Hello,
> > 
> > the eventfd test creates some files in the current directory. I think it should be creating the files in a temporary directory instead, as is already the standard with other LTP tests, because the current might be nonwriteable and the user might not want the files left there.
> > 
> > Regards
> >     Jiri Palecek
> > 
> > Signed-off-by: Jiri Palecek <jpalecek@web.de>
> 
> Thanks. 
> 
> Recently i have seen some patches on LKML from Davide on the change for
> eventfd() interface. Could you please verify how they will affect our
> tests, and, make changes if necessary ?
> http://lkml.org/lkml/2009/6/24/590,

Any thoughts for this ?

Regards--
Subrata

> 
> Regards--
> Subrata
> 
> > ---
> >  testcases/kernel/syscalls/eventfd/eventfd01.c |    3 +++
> >  1 files changed, 3 insertions(+), 0 deletions(-)
> > 
> > diff --git a/testcases/kernel/syscalls/eventfd/eventfd01.c b/testcases/kernel/syscalls/eventfd/eventfd01.c
> > index ee09752..0eed8d1 100644
> > --- a/testcases/kernel/syscalls/eventfd/eventfd01.c
> > +++ b/testcases/kernel/syscalls/eventfd/eventfd01.c
> > @@ -759,6 +759,8 @@ static void setup(void)
> >  	if (tst_kvercmp(2, 6, 22) < 0)
> >  		tst_brkm(TCONF, cleanup, "2.6.22 or greater kernel required");
> > 
> > +	/* Create a temporary directory & chdir there */
> > +	tst_tmpdir();
> >  	/* Pause if that option was specified
> >  	 * TEST_PAUSE contains the code to fork the test with the -c option.
> >  	 */
> > @@ -776,6 +778,7 @@ static void cleanup(void)
> >  	 */
> >  	TEST_CLEANUP;
> > 
> > +	tst_rmdir();
> >  	/* exit with return code appropriate for results */
> >  	tst_exit();
> >   /*NOTREACHED*/}
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-06-30  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200906232049.n5NKne0h007108@e5.ny.us.ibm.com>
2009-06-25  9:09 ` [LTP] [PATCH] Run the eventfd test in a temporary directory, because it creates some files Subrata Modak
2009-06-30  7:41   ` Subrata Modak [this message]
2009-06-30 14:41     ` Davide Libenzi
2009-06-30 14:50       ` Subrata Modak
2008-12-29 13:48 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=1246347667.4819.27.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=davidel@xmailserver.org \
    --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