From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] test with aio02 is failing with safe_macros.c:223: BROK: aio02.c:130: open(file, 16961, 0644) failed: EINVAL (22)
Date: Wed, 12 Feb 2020 13:36:53 +0800 [thread overview]
Message-ID: <5E438EF5.1050800@cn.fujitsu.com> (raw)
In-Reply-To: <588cc009-d46f-4070-7b14-ea81f8dc6b76@cn.fujitsu.com>
On 2020/2/11 18:55, Yang Xu wrote:
>
> on 2020/02/11 18:25, Xiao Yang wrote:
>>
>> On 2/11/20 6:01 PM, Pankaj Vinadrao Joshi wrote:
>>> Hi sir,
>>> I am begginer can you tell how i can check if tmpfs is mounted on
>>> /tmp in your enviroment?
>>
>> Hi,
>>
>>
>> You can use df/mount command to do check, as below:
>>
>> -----------------------------------------------------------------
>>
>> [root@Fedora-30-vm linux]# df -h | grep '/tmp'
>> tmpfs 993M 4.0K 993M 1% /tmp
>>
>> [root@Fedora-30-vm linux]# mount | grep '/tmp'
>> tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel)
>>
>> ------------------------------------------------------------------
>>
>>>
>>> Sir if you have two minutes of time can you elaborate it whats its
>>> meaning?
>>
>> aio02 uses open(O_WRONLY | O_TRUNC | O_DIRECT | O_LARGEFILE |
>> O_CREAT) to
>>
>> create test file in default /tmp directory and ****O_DIRECT flag may
>> not be supported
>>
>> by tmpfs so calling open() returns EINVAL.
>>
> Hi Xiao
> I think we should add a check or use a valid filesystem to test in
> this case.
Hi Xu,
Sorry for my late reply.
Sure, we need to fix the issue indeed.
Thanks,
Xiao Yang
>
> Best Regards
> Yang Xu
>>
>> Thanks,
>>
>> Xiao Yang
>>
>>>
>>>
>>> Thank you ?
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Xiao Yang <ice_yangxiao@163.com>
>>> *Sent:* Tuesday, February 11, 2020 3:04 PM
>>> *To:* Pankaj Vinadrao Joshi <Pankaj.VJ@exaleapsemi.com>
>>> *Subject:* Re: [LTP] test with aio02 is failing with
>>> safe_macros.c:223: BROK: aio02.c:130: open(file, 16961, 0644)
>>> failed: EINVAL (22)
>>>
>>> Hi,
>>>
>>>
>>> Could you check if tmpfs is mounted on /tmp in your enviroment?
>>>
>>> It seems that tmpfs cannot support O_DIRECT flag and creating file
>>> with O_DIRECT in tmpfs triggers the error.
>>>
>>> Perhaps, you can fix the error by mounting normal filesystem(e.g.
>>> ext4/xfs) on /tmp for now.
>>>
>>>
>>> Thanks,
>>>
>>> Xiao Yang
>>>
>>> On 2/11/20 4:31 PM, Pankaj Vinadrao Joshi wrote:
>>>> Hi,
>>>> i am running aio02 test on my RISC v machine,my testing is getting
>>>> failed with the message
>>>> *safe_macros.c:223: BROK: aio02.c:130: open(file,16961,0644)
>>>> failed: EINVAL (22)*
>>>>
>>> [EXT]
>>
>>
>
>
>
prev parent reply other threads:[~2020-02-12 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 8:31 [LTP] test with aio02 is failing with safe_macros.c:223: BROK: aio02.c:130: open(file, 16961, 0644) failed: EINVAL (22) Pankaj Vinadrao Joshi
[not found] ` <f6cf7d37-cf31-7448-0bea-035eb48f2f79@163.com>
[not found] ` <BMXPR01MB2999C5C6166A34812CFA3727EE180@BMXPR01MB2999.INDPRD01.PROD.OUTLOOK.COM>
2020-02-11 10:25 ` Xiao Yang
2020-02-11 10:55 ` Yang Xu
2020-02-12 5:36 ` Xiao Yang [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=5E438EF5.1050800@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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