From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: shyju pv <shyju.pv@huawei.com>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Test case send01 fails in kernel version 3.6-rc1, rc2 and rc3
Date: Wed, 3 Oct 2012 14:32:50 +0200 [thread overview]
Message-ID: <20121003123250.GA8435@rei> (raw)
In-Reply-To: <564795434.6124572.1349265888804.JavaMail.root@redhat.com>
Hi!
> > The usuall concensus for such case is to change expected return
> > values
> > depending on the kernel version (see for example tst_kvercmp() in
> > testcases/kernel/syscalls/sysctl/sysctl03.c). Which is the best
> > solution
> > I can come up with.
> >
> > On the other hand we don't bother to work with rc kernels they change
> > far to often.
> >
> > Does this behave same on released linux 3.6?
>
> I believe it does. I just tested with RHEL7 kernel based on 3.6, which is at this point
> very close to vanilla (+- few changes in build scripts and config).
>
> # ./send01
> send01 1 TPASS : bad file descriptor successful
> send01 2 TPASS : invalid socket successful
> send01 3 TPASS : invalid send buffer successful
> send01 4 TPASS : UDP message too big successful
> send01 5 TPASS : local endpoint shutdown successful
> send01 6 TFAIL : invalid flags set ; returned -1 (expected -1), errno 95 (expected 14)
> # cd ../sendto/
> # ./sendto01
> sendto01 1 TPASS : bad file descriptor successful
> sendto01 2 TPASS : invalid socket successful
> sendto01 3 TPASS : invalid send buffer successful
> sendto01 4 TPASS : connected TCP successful
> sendto01 5 TPASS : not connected TCP successful
> sendto01 6 TPASS : invalid to buffer length successful
> sendto01 7 TPASS : invalid to buffer successful
> sendto01 8 TPASS : UDP message too big successful
> sendto01 9 TPASS : local endpoint shutdown successful
> sendto01 10 TFAIL : invalid flags set ; returned -1 (expected 0), errno 95 (expected 32)
> # cd ../sendmsg/
> # ./sendmsg01
> sendmsg01 1 TPASS : bad file descriptor successful
> sendmsg01 2 TPASS : invalid socket successful
> sendmsg01 3 TPASS : invalid send buffer successful
> sendmsg01 4 TPASS : connected TCP successful
> sendmsg01 5 TPASS : not connected TCP successful
> sendmsg01 6 TPASS : invalid to buffer length successful
> sendmsg01 7 TPASS : invalid to buffer successful
> sendmsg01 8 TPASS : UDP message too big successful
> sendmsg01 9 TPASS : local endpoint shutdown successful
> sendmsg01 10 TPASS : invalid iovec pointer successful
> sendmsg01 11 TPASS : invalid msghdr pointer successful
> sendmsg01 12 TPASS : rights passing successful
> sendmsg01 13 TPASS : invalid flags set w/ control successful
> sendmsg01 14 TFAIL : invalid flags set ; returned -1 (expected 0), errno 95 (expected 95)
> sendmsg01 15 TPASS : invalid cmsg length successful
> sendmsg01 16 TPASS : invalid cmsg pointer successful
Okay then I will prepare patch. Stay tuned.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-10-03 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 10:30 [LTP] Test case send01 fails in kernel version 3.6-rc1, rc2 and rc3 shyju pv
2012-08-27 11:16 ` Jan Stancek
2012-10-03 11:40 ` chrubis
[not found] ` <564795434.6124572.1349265888804.JavaMail.root@redhat.com>
2012-10-03 12:32 ` chrubis [this message]
2012-10-10 13:09 ` chrubis
2012-10-10 13:32 ` chrubis
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=20121003123250.GA8435@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=shyju.pv@huawei.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