public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Shyju PV <shyju.pv@huawei.com>
To: ltp-list@lists.sourceforge.net
Cc: 'Sanil kumar' <sanil.kumar@huawei.com>, nagamani.mantha@huawei.com
Subject: [LTP] sendto syscall fails because of the error value missmatch from 3.6-rc1 kernel onwards
Date: Sat, 25 Aug 2012 17:12:09 +0530	[thread overview]
Message-ID: <043301cd82b6$a9809f10$fc81dd30$@pv@huawei.com> (raw)
In-Reply-To: <mailman.414062.1338991083.27891.ltp-list@lists.sourceforge.net>

LTP_Version: 2012-06-14 
LTP Test case: sendto01 
Description : Verifies the sendto syscall errorno for various failure cases 
Failure Analysis : when the invalid flag is set, The error no EOPNOTSUPP
(95) and syscall returns 0 .instead LTP expects EPIPE (32) and the syscall
return value as -1. 
Fix : Modify  the LTP code with respect the the system return values of the
latest kernel(3.6-rc1) 
Test case passed in Kernel 3.5 
Failed from  3.6-rc1,rc2and rc3 

Test output :: <<<test_output>>> 
incrementing stop 
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) 
<<<execution_status>>> 
initiation_status="ok" 
duration=0 termination_type=exited termination_id=1 corefile=no 
cutime=0 cstime=0 
<<<test_end>>> 
INFO: ltp-pan reported some tests FAIL

Shyju


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

       reply	other threads:[~2012-08-25 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.414062.1338991083.27891.ltp-list@lists.sourceforge.net>
2012-08-25 11:42 ` Shyju PV [this message]
2012-08-26 11:18   ` [LTP] sendto syscall fails because of the error value missmatch from 3.6-rc1 kernel onwards Jan Stancek

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='043301cd82b6$a9809f10$fc81dd30$@pv@huawei.com' \
    --to=shyju.pv@huawei.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=nagamani.mantha@huawei.com \
    --cc=sanil.kumar@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