From: Kang Kai <Kai.Kang@windriver.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] aio_read/8-1.c fails
Date: Thu, 8 Mar 2012 16:29:44 +0800 [thread overview]
Message-ID: <4F586DF8.1030008@windriver.com> (raw)
In-Reply-To: <4F584AF1.3010909@windriver.com>
On 2012年03月08日 14:00, Kang Kai wrote:
> Hi All,
>
> aio_read/8-1.c "fills in an aiocb with a NULL aio_buf" and then expect
> that the operation is not succesfully queued.
> It fails that aio_read() always return 0. And I checked the posix spec
> and didn't find that an aiocb with NULL aio_buf will cause enqueue fails.
> So is this case valid?
So does the case aio_write/6-1.c.
>
> Thanks,
> Kai
>
> ------------------------------------------------------------------------------
> Virtualization& Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-03-08 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 6:00 [LTP] aio_read/8-1.c fails Kang Kai
2012-03-08 8:29 ` Kang Kai [this message]
2012-03-08 11:54 ` Cyril Hrubis
[not found] ` <4F5969C9.2020508@windriver.com>
2012-03-09 13:38 ` 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=4F586DF8.1030008@windriver.com \
--to=kai.kang@windriver.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