From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/mq_open: fix limits for queues_max
Date: Wed, 15 Feb 2017 13:19:21 -0500 (EST) [thread overview]
Message-ID: <1608152395.5261795.1487182761583.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <956936356.5228861.1487177447794.JavaMail.zimbra@redhat.com>
> I'm looking at results of kernel-2.6.32-694.el6 (6.9), and it's passing:
> <<<test_start>>>
> tag=mq_open01 stime=1487065446
> cmdline="mq_open01"
> contacts=""
> analysis=exit
> <<<test_output>>>
> EXPECT: return value(ret)=(N >= 0) errno=0 (Success)
> RESULT: return value(ret)= 7 errno=0 (Success)
> mq_open01 0 TINFO : (case00) START
> mq_open01 0 TINFO : mq_maxmsg E:20, R:20
> mq_open01 0 TINFO : mq_msgsize E:16384, R:16384
> mq_open01 0 TINFO : (case00) END => OK
> mq_open01 1 TPASS : mq_open call succeeded
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=0 corefile=no
> cutime=0 cstime=0
> <<<test_end>>>
Oh, I see, the testcase has changed:
8e49ed6b0fa2 "syscalls/mq_open: fix old tests + convert to use new API"
I was using ltp-20170116. git HEAD fails for me too:
# ./mq_open01
tst_test.c:812: INFO: Timeout per run is 0h 05m 00s
mq_open01.c:230: INFO: queue name "/test_mqueue"
mq_open01.c:260: PASS: NORMAL returned: 3: SUCCESS
mq_open01.c:230: INFO: queue name "/test_mqueue"
mq_open01.c:260: PASS: NORMAL returned: 3: SUCCESS
mq_open01.c:230: INFO: queue name "/caaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
mq_open01.c:260: PASS: NORMAL returned: 3: SUCCESS
mq_open01.c:230: INFO: queue name "/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
mq_open01.c:277: PASS: NORMAL returned: -1: ENAMETOOLONG
mq_open01.c:230: INFO: queue name ""
mq_open01.c:277: PASS: NORMAL returned: -1: EINVAL
mq_open01.c:230: INFO: queue name "/test_mqueue"
mq_open01.c:277: PASS: NORMAL returned: -1: EACCES
mq_open01.c:230: INFO: queue name "/test_mqueue"
mq_open01.c:277: PASS: NORMAL returned: -1: EEXIST
mq_open01.c:230: INFO: queue name "/test_mqueue"
mq_open01.c:277: PASS: NO_FILE returned: -1: EMFILE
mq_open01.c:230: INFO: queue name "/notexist"
mq_open01.c:277: PASS: NORMAL returned: -1: ENOENT
mq_open01.c:230: INFO: queue name "/test_mqueue"
safe_file_ops.c:301: BROK: Failed to close FILE '/proc/sys/fs/mqueue/queues_max' at mq_open01.c:177: EINVAL
So, yes, I'd prefer to apply Xiao's patch. It shouldn't affect
test on newer kernels, and we can test older ones too.
Regards,
Jan
next prev parent reply other threads:[~2017-02-15 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 12:42 [LTP] [PATCH] syscalls/mq_open: fix limits for queues_max Xiao Yang
2017-02-15 1:26 ` Xiao Yang
2017-02-15 15:24 ` Cyril Hrubis
2017-02-15 16:50 ` Jan Stancek
2017-02-15 18:19 ` Jan Stancek [this message]
2017-02-16 9:37 ` Cyril Hrubis
2017-02-16 1:20 ` Xiao Yang
2017-02-16 2:38 ` [LTP] [PATCH v2] " Xiao Yang
2017-02-16 9:28 ` Cyril Hrubis
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=1608152395.5261795.1487182761583.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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