mrfs_fstime failure

[Joel Sherrill]

On 4/1/2014 5:03 PM, Chris Johns wrote:
> On 2/04/2014 6:44 am, Joel Sherrill wrote:
>> Hi
>>
>> I think this is a long standing failure.
>>
>> *** BEGIN OF TEST FSTIME RFS ***
>> Initializing filesystem RFS
>> Sleep a few seconds
>> ../../../../../../../rtems/c/src/../../testsuites/fstests/mrfs_fstime/../fstime/test.c:
>> 131 st.st_ctime == st.st_mtime
>>
>> When I break at end of stat, I see this.
>>
>> (gdb) p *buf
>> $1 = {st_dev = 34401048, st_ino = 2, st_mode = 16877, st_nlink = 1,
>> st_uid = 0, st_gid = 0, st_rdev = 0, st_size = 512, st_atim = {
>>      tv_sec = 567993600, tv_nsec = 0}, st_mtim = {tv_sec = 567993600,
>> tv_nsec = 0}, st_ctim = {tv_sec = 567993606, tv_nsec = 0},
>>    st_blksize = 512, st_blocks = 1}
>>
>> Something is happening in test.c with gdb and I can't print the stat buf.
>>
>> Any ideas? Since this is a generic failure, it would be good to
>> eliminate it.
>>
> It is specific to the RFS as far as I know. The code in the test says ...
>
>    /*
>     * If O_CREAT is set and the file did not previously exist, upon
>     * successful completion, open() shall mark for update the st_atime,
>     * st_ctime, and st_mtime fields of the file and the st_ctime and
>     * st_mtime fields of the parent directory.
>     */
>
> Does this apply to the creation of any node in the file system ?
We would have to find the place in the POSIX standard. This statements
like it is
from http://pubs.opengroup.org/onlinepubs/009695399/functions/fopen.html.

This would imply to me that it should but can the FAT filesystem support
this?

Are you hinting that it is generic code which should be in the system
call layer?
> Chris

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985