public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: JANAK DESAI <janak@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	linux-arch@vger.kernel.org, Ulrich Drepper <drepper@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>,
	David Howells <dhowells@redhat.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	Christoph Lameter <christoph@lameter.com>
Subject: Re: new syscalls
Date: Tue, 24 Jan 2006 18:44:10 -0500	[thread overview]
Message-ID: <43D6BBCA.3090706@us.ibm.com> (raw)
In-Reply-To: <20060118133629.1cda96fd.akpm@osdl.org>

Andrew Morton wrote:

>"Luck, Tony" <tony.luck@intel.com> wrote:
>  
>
>>>Various new syscalls which are trickling their way Linuswards and will need
>>>testing and wiring up once they get there:
>>>      
>>>
>>Are there test-suites for any/all of these new calls?
>>
>>    
>>
>
>That's an excellent point.
>
>Guys, architecture maintainers need test suites to verify that the syscalls
>actually work as they wire them up.  Please share.  A stable URL would be
>preferred - something which can go into the changlog or conceivably into
>the kernel source.
>
>Thanks.
>
>  
>
Here is the link to a program for testing unshare system call.

http://prdownloads.sourceforge.net/audit/unshare_test.c?download

Please note that because of a problem in rmdir associated with
bind mounts and clone with CLONE_NEWNS, the test fails while
trying to remove temporary test directory. You can remove that
temporary directory by doing rmdir, twice, from the command line.
The first will fail with EBUSY, but the second will succeed. I have
reported the problem to Ram Pai and Al Viro with a small program
which reproduces the problem. Al told us yesterday that he will
be looking at the problem soon. I have tried multiple rmdirs from
the unshare_test program itself, but for some reason that is not
working. Doing two rmdirs from command line does seem to
remove the directory.

Please let me know if you have trouble downloading/running
the program.

-Janak


  parent reply	other threads:[~2006-01-24 23:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 18:55 new syscalls Luck, Tony
2006-01-18 21:36 ` Andrew Morton
2006-01-18 21:48   ` Ulrich Drepper
2006-01-18 21:58     ` David S. Miller
2006-01-18 21:53   ` David Woodhouse
2006-01-18 21:58     ` David S. Miller
2006-01-20 10:04     ` Andi Kleen
2006-01-20 10:15       ` David S. Miller
2006-01-23  6:44         ` David Woodhouse
2006-01-23  9:58         ` Heiko Carstens
2006-01-19  1:17   ` Davide Libenzi
2006-01-19  1:26     ` David S. Miller
2006-01-19  5:00       ` David Woodhouse
2006-01-19  1:28     ` Andrew Morton
2006-01-19 21:48       ` Davide Libenzi
2006-01-20  0:13         ` Davide Libenzi
2006-01-20  0:23           ` Ulrich Drepper
2006-01-20  0:34             ` Davide Libenzi
2006-01-19  1:19   ` Christoph Lameter
2006-01-19  2:30     ` Andi Kleen
2006-01-19 13:50   ` JANAK DESAI
2006-01-22 17:45   ` JANAK DESAI
2006-01-24 23:44   ` JANAK DESAI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-18  3:29 Andrew Morton
2006-01-18  3:38 ` Andi Kleen
2006-01-20  9:43   ` Heiko Carstens
2006-01-20  9:48     ` Andi Kleen
2006-01-20  9:49     ` David S. Miller

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=43D6BBCA.3090706@us.ibm.com \
    --to=janak@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=christoph@lameter.com \
    --cc=davidel@xmailserver.org \
    --cc=dhowells@redhat.com \
    --cc=drepper@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /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