public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: gaowanlong@cn.fujitsu.com
Cc: ltp-list@lists.sourceforge.net, Zhenfeng.Zhao@windriver.com
Subject: Re: [LTP] [PATCH] aio_suspend/3-1: wait all aio_write complete
Date: Mon, 6 Aug 2012 17:30:05 +0800	[thread overview]
Message-ID: <501F8E9D.4070403@windriver.com> (raw)
In-Reply-To: <501F8139.3010709@cn.fujitsu.com>

On 2012年08月06日 16:32, Wanlong Gao wrote:
> On 08/06/2012 04:19 PM, Kang Kai wrote:
>> After aio_suspend, wait all aio_write operations to complete.
>>
>> If don't do that, it fails with "Segmentation fault" on routerstation(mips)
>> board randomly about in 1000 continuous test. The reason may be some
>> aio_writes don't complete before close the file, that cause some resouse
>> don't be released and finally cause segment fault.
>>
>> Signed-off-by: Kang Kai<kai.kang@windriver.com>
>> ---
>>   .../conformance/interfaces/aio_suspend/3-1.c       |   12 ++++++++++++
>>   1 files changed, 12 insertions(+), 0 deletions(-)
>>
>> diff --git a/testcases/open_posix_testsuite/conformance/interfaces/aio_suspend/3-1.c b/testcases/open_posix_testsuite/conformance/interfaces/aio_suspend/3-1.c
>> index 15120e1..e8e9705 100644
>> --- a/testcases/open_posix_testsuite/conformance/interfaces/aio_suspend/3-1.c
>> +++ b/testcases/open_posix_testsuite/conformance/interfaces/aio_suspend/3-1.c
>> @@ -46,6 +46,7 @@ int main()
>>   	struct aiocb aiocb[NAIOCB];
>>   	const struct aiocb *list[NENT];
>>   	int i;
>> +	int ret;
>>
>>   	if (sysconf(_SC_ASYNCHRONOUS_IO)<  200112L)
>>   		return PTS_UNSUPPORTED;
>> @@ -87,6 +88,17 @@ int main()
>>   		exit(PTS_FAIL);
>>   	}
>>
>> +	for (i = 0; i<  NAIOCB; ++i) {
>> +		do {
>> +			usleep(10000);
>> +			ret = aio_error(&aiocb[i]);
>> +		} while (ret == EINPROGRESS);
>> +		if (aio_return(&aiocb[i]) == -1) {

Hi Wanlong,

> Why do you check the return value here? and did you test this patch on your mips machine?
I test it on mips for 4x1000 times and x86_64, and the results are fine.
With no other operation, when aio_write complete, it should succeed. So 
I use aio_return to check the return values.

Regards,
Kai

>
> Thanks,
> Wanlong Gao
>
>> +			printf(TNAME " Error at aio_return(): %s\n", strerror(errno));
>> +			exit(PTS_FAIL);
>> +		}
>> +	}
>> +
>>   	close(fd);
>>   	printf("Test PASSED\n");
>>   	return PTS_PASS;
>>
>


------------------------------------------------------------------------------
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-06  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  8:19 [LTP] V2: patch for aio_suspend/3-1 Kang Kai
2012-08-06  8:19 ` [LTP] [PATCH] aio_suspend/3-1: wait all aio_write complete Kang Kai
2012-08-06  8:32   ` Wanlong Gao
2012-08-06  9:30     ` Kang Kai [this message]
2012-08-06  9:37       ` Wanlong Gao
2012-08-06 10:04         ` Kang Kai

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=501F8E9D.4070403@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=gaowanlong@cn.fujitsu.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