From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] mqns tests are failing
Date: Wed, 28 Apr 2010 15:03:01 -0500 [thread overview]
Message-ID: <20100428200301.GA16632@us.ibm.com> (raw)
In-Reply-To: <k2t364299f41004281001v356f74a7h17a5c160ec9efbc2@mail.gmail.com>
Quoting Garrett Cooper (yanegomi@gmail.com):
> On Wed, Apr 28, 2010 at 6:42 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > Quoting Garrett Cooper (yanegomi@gmail.com):
> >> On Wed, Apr 28, 2010 at 1:54 AM, Munipradeep Beerakam
> >> <mpradeep@linux.vnet.ibm.com> wrote:
> >> > Hi,
> >> >
> >> > I noticed that mqns test cases are failing. I am using March 2010 LTP.
> >> > After changing mq_open syscall in mqns_01.c file, test is passing. Same
> >> > thing is happening w.r.t. other mqns test cases. Below is the change I
> >> > made.
> >> >
> >> > Changed
> >> > mqd = syscall(__NR_mq_open, SLASH_MQ1, O_RDWR|O_CREAT|O_EXCL,0777,
> >> > NULL);
> >> >
> >> > to
> >> > mqd = mq_open(SLASH_MQ1, O_RDWR|O_CREAT|O_EXCL, 0777, NULL);
> >> >
> >> > Failure output I got is below:
> >> > # ./mqns_01
> >> > posixmq_namespace_01 0 TINFO : Testing posix mq namespaces through
> >> > unshare(2).
> >> >
> >> > mq_open: Permission denied
> >> > posixmq_namespace_01 1 TFAIL : mq_open failed
> >> >
> >> > After changing as above, I got the below output:
> >> > # ./mqns_01
> >> > posixmq_namespace_01 0 TINFO : Testing posix mq namespaces through
> >> > unshare(2).
> >> >
> >> > posixmq_namespace_01 0 TINFO : Checking namespaces isolation from
> >> > parent to child
> >> >
> >> > posixmq_namespace_01 1 TPASS : child process didn't find mqueue
> >> >
> >> > So, my question is that what is the difference between the two, i.e.,
> >> > the previous one and the changed one. Both are calling the same mq_open
> >
> > See http://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg09073.html
> > for the ansswer.
> >
> >> > system call. But first one is failing whereas the second one is
> >> > succeeding.
> >> >
> >> > So, do we need to modify all mqns test cases to the new form?
> >>
> >> Track down the execution path by first starting with glibc. It
> >> might be a library vs kernel mismatch or a bug. Make sure that the
> >> syscall number matches per your architecture, determine whether or not
> >> your architecture has issues executing code in a biarch manner (64-bit
> >> on 32-bit) if it applies.
> >> HTH,
>
> Ah, forgot about that...
So had I :) And I think I'd assumed someone else would push the
patch you suggested. I'll go ahead and send one later today.
-serge
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2010-04-28 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 8:54 [LTP] mqns tests are failing Munipradeep Beerakam
2010-04-28 9:13 ` Garrett Cooper
2010-04-28 13:42 ` Serge E. Hallyn
2010-04-28 17:01 ` Garrett Cooper
2010-04-28 20:03 ` Serge E. Hallyn [this message]
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=20100428200301.GA16632@us.ibm.com \
--to=serue@us.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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