From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Wei Yongjun <yjwei@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [QUESTION] about test execve04 which testing for EMFILE
Date: Tue, 26 May 2009 17:52:52 +0530 [thread overview]
Message-ID: <1243340572.6293.23.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <4A1BB9F6.6050107@cn.fujitsu.com>
On Tue, 2009-05-26 at 17:44 +0800, Wei Yongjun wrote:
> Subrata Modak wrote:
> > On Fri, 2009-05-22 at 17:26 +0800, Wei Yongjun wrote:
> >
> >> recently kernel commit e7b9b550f53e81ea38e71d322d6f95730df058a2
> >> has removed the file get code. The execve syscall will never
> >> return EMFILE.
> >>
> >> Call to execve() will be suceess even if the the process has the
> >> maximum number of files open, because execve() never open any file.
> >>
> >> Can anyone tell me what does this test case test for? It be wrote
> >> base on which document? Just the man page?
> >>
> >
> > * DESCRIPTION
> > * Testcase to check execve(2) sets errno to EMFILE correctly
> > *
> > * ALGORITHM
> > * Get the configured file descriptor table size. open(2) files to
> > fill
> > * up the file descriptor table. Once file descriptor table is full,
> > * an attempt to execve(2) any other executable fails with EMFILE.
> >
> > is what the source description says. Can you please execute the test
> > against that kernel commit and share the results with/without commits ?
> >
>
> Test without that commit:
> # ./execve04 -F ./test3
> execve04 1 PASS : Expected failure - 24 : Too many open files
>
> Test with that commit:
> # ./execve04 -F ./test3
> <program name unknown>: error while loading shared libraries: libc.so.6:
> cannot open shared object file: Error 24
> execve04 1 FAIL :
> execve(/home/weiyj/ltp/testcases/kernel/syscalls/execve/./test3) failed:
> expected EMFILE(24), got 127 (Key has expired)
>
> Test with that commit but I compiled test3 with --static:
> # gcc test3.c -o test3 --static
> # ./execve04 -F ./test3
> Hello World
> execve04 1 FAIL :
> execve(/home/weiyj/ltp/testcases/kernel/syscalls/execve/./test3) failed:
> expected EMFILE(24), got 0 (Success)
>
> The latest kernel do execve(2) without get file descriptor, it only
> need one file struct. It seem that this test is obsoleted.
Lets remove then. Send a patch to do so.
Regards--
Subrata
>
>
------------------------------------------------------------------------------
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 asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-05-26 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 9:26 [LTP] [QUESTION] about test execve04 which testing for EMFILE Wei Yongjun
2009-05-25 16:14 ` Subrata Modak
2009-05-26 9:44 ` Wei Yongjun
2009-05-26 12:22 ` Subrata Modak [this message]
2009-05-27 3:48 ` Wei Yongjun
2009-05-27 14:23 ` 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=1243340572.6293.23.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yjwei@cn.fujitsu.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