From: Anders Roxell <anders.roxell@linaro.org>
To: richard_c_haines@btinternet.com, paul@paul-moore.com
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov,
linux-kernel@vger.kernel.org
Subject: Regression found when running LTP connect01 on next-20180301
Date: Thu, 1 Mar 2018 09:33:16 +0100 [thread overview]
Message-ID: <20180301083316.GA6779@localhost.localdomain> (raw)
Hi,
I was running LTP's testcase connect01 [1] and found a regression in linux-next
(next-20180301). Bisect gave me this patch as the problematic patch (sha
d452930fd3b9 "selinux: Add SCTP support") on a x86 target.
Output from the test(LTP release 20180118):
$ cd /opt/ltp/
$ cat runtest/syscalls |grep connect01>runtest/connect-syscall
$ ./runltp -pq -f connect-syscall
"
Running tests.......
connect01 1 TPASS : bad file descriptor successful
connect01 2 TPASS : invalid socket buffer successful
connect01 3 TPASS : invalid salen successful
connect01 4 TPASS : invalid socket successful
connect01 5 TPASS : already connected successful
connect01 6 TPASS : connection refused successful
connect01 7 TFAIL : connect01.c:146: invalid address family ; returned -1 (expected -1), errno 22 (expected 97)
INFO: ltp-pan reported some tests FAIL
LTP Version: 20180118
"
The output from the test expected 97 and we received 22, can you please
elaborate on what have been changed?
Cheers,
Anders
[1] https://github.com/linux-test-project/ltp/blob/20180118/testcases/kernel/syscalls/connect/connect01.c#L146
next reply other threads:[~2018-03-01 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 8:33 Anders Roxell [this message]
2018-03-01 13:42 ` Regression found when running LTP connect01 on next-20180301 Paul Moore
2018-03-01 14:36 ` Richard Haines
2018-03-01 16:20 ` Paul Moore
2018-03-01 18:03 ` Paul Moore
2018-03-02 16:55 ` Richard Haines
2018-03-01 20:01 ` Anders Roxell
2018-03-01 20:17 ` Paul Moore
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=20180301083316.GA6779@localhost.localdomain \
--to=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@tycho.nsa.gov \
/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;
as well as URLs for NNTP newsgroup(s).