From: Kang Kai <Kai.Kang@windriver.com>
To: gaowanlong@cn.fujitsu.com,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Posix test case mmap/31-1 fails on Linux/eglibc
Date: Wed, 4 Jan 2012 11:32:27 +0800 [thread overview]
Message-ID: <4F03C84B.80906@windriver.com> (raw)
In-Reply-To: <4F03C02A.8090304@cn.fujitsu.com>
On 2012年01月04日 10:57, Wanlong Gao wrote:
> On 01/04/2012 10:50 AM, Yasuaki Ishimatsu wrote:
>
>> Hi Gao,
>>
>> 2012/01/04 11:05, Wanlong Gao wrote:
>>> On 01/04/2012 09:37 AM, Yasuaki Ishimatsu wrote:
>>>
>>>> Hi Kai,
>>>>
>>>> 2011/12/28 19:55, Kang Kai wrote:
>>>>> Hi all,
>>>>>
>>>>> I run mmap/31-1 failed with ENOMEM on linux, with error message:
>>>>> off: fffffffffffff000, len: fffffffffffff000
>>>>> Test FAIL: expect EOVERFLOW but get other error: Cannot allocate memory
>>>>>
>>>>> But compare to mmap/24-2, it mmap() the same length but pass. Its output:
>>>>> available memory: 18446744073709551615
>>>>> addr: 7f78c54fa000, len: ffffffffffffffff
>>>>> addr: 7f78c54fa000, len: fffffffffffff000
>>>>> Test Pass: mmap/24-2.c Get ENOMEM: Cannot allocate memory
>>>>>
>>>>> So I suppose that mmap/31-1 may need update, but I don't know how to
>>>>> make mmap() overflow as expect.
>>>>> Any suggestion is appreciated.
>>>> I don't think mmap/31-1 need update since it is Linux Kernel's problem,
>>>> not the test's problem. The problem is being discussed on LKML.
>>>>
>>>> https://lkml.org/lkml/2011/12/22/85
>>>
>>> But it seems that the patch was not acceptable.
>> As you say, it has not been accepted yet.
>> But I think Linux will be fixed to return EOVERFLOW in mmap/31-1's test
>> in the near future.
>
> Yeah, agree, so we need not update this test case now and wait for a while
> to let the kernel bug to be fixed.
OK, thank you very much!
>
>> Regards,
>> Yasuaki Ishimatsu
>>
>>> Thanks
>>> -Wanlong Gao
>>>
>>>> Regards,
>>>> Yasuaki Ishimatsu
>>>>
>>>>> Regards,
>>>>> Kai
>>>
>>>
>>>
>>
>
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-01-04 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 10:55 [LTP] Posix test case mmap/31-1 fails on Linux/eglibc Kang Kai
2011-12-28 18:16 ` Cyril Hrubis
2012-01-04 1:37 ` Yasuaki Ishimatsu
2012-01-04 2:05 ` Wanlong Gao
2012-01-04 2:50 ` Yasuaki Ishimatsu
2012-01-04 2:57 ` Wanlong Gao
2012-01-04 3:32 ` Kang Kai [this message]
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=4F03C84B.80906@windriver.com \
--to=kai.kang@windriver.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=isimatu.yasuaki@jp.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