public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net, Nitin Yadav <Nitin.Yadav@mphasis.com>
Subject: Re: [LTP] [PATCH] io_submit: uninitialized iocb may not return	-EINVAL
Date: Tue, 16 Oct 2012 12:11:01 +0200	[thread overview]
Message-ID: <20121016101101.GB9320@rei.Home> (raw)
In-Reply-To: <82432993.665989.1350370438315.JavaMail.root@redhat.com>

Hi!
> Notice that return value is positive (1). So it could be that some random data
> succeeded and one iocb was actually submitted.

Well I think that if you pass random data to the kernel the only
assumption that may hold is that this action should not bring the system
down (unless of course you happen to initiate shutdown).

From this point of view calling libcalls/syscalls with random values and
asserting certain results makes a little sense.

-- 
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

  reply	other threads:[~2012-10-16 10:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  9:52 [LTP] crashme:fork12 test may kill other process that is not forked child 羅秉鈞
2012-06-29  7:45 ` Wanlong Gao
2012-10-09  6:08   ` [LTP] [PATCH] io_submit: uninitialized iocb may not return -EINVAL Nitin Yadav
2012-10-16  2:31     ` Wanlong Gao
2012-10-16  6:53       ` Jan Stancek
2012-10-16 10:11         ` chrubis [this message]
     [not found]           ` <E351E450E8B9F54684A699D42DC5ADF2263AF477@MPBAGVEX02.corp.mphasis.com>
     [not found]             ` <E351E450E8B9F54684A699D42DC5ADF22640E162@MPBAGVEX02.corp.mphasis.com>
2012-10-17 12:44               ` [LTP] [PATCH] io_submit: uninitialized iocb may notreturn-EINVAL chrubis
2012-06-29 16:22 ` [LTP] crashme:fork12 test may kill other process that is not forked child chrubis
  -- strict thread matches above, loose matches on Subject: below --
2012-07-05 13:03 [LTP] [PATCH] io_submit: uninitialized iocb may not return -EINVAL Nitin Yadav
2012-03-14 14:53 Jan Stancek
2012-03-15  1:09 ` Wanlong Gao
2012-03-15  2:09   ` Wanlong Gao
2012-03-15  7:48   ` Jan Stancek
2012-03-15  7:56     ` Wanlong Gao

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=20121016101101.GB9320@rei.Home \
    --to=chrubis@suse.cz \
    --cc=Nitin.Yadav@mphasis.com \
    --cc=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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