From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Amit Sahrawat <amit.sahrawat83@gmail.com>
Subject: Re: [PATCH 2/3] fat: fix time updates for create and delete
Date: Thu, 15 Nov 2012 16:18:39 +0900 [thread overview]
Message-ID: <87txsr49m8.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd84jVdb99qAqda_NGEDUg1G1F9aLGQV+Kj3xcTBN=FxwQ@mail.gmail.com> (Namjae Jeon's message of "Thu, 15 Nov 2012 16:02:26 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
> 1)If we consider the code for FAT and MSDOS to be same with respect to
> timing updates - there there is difference in code as mentioned below:
> a) For:vfat_rmdir()
> inode->i_mtime = inode->i_atime = CURRENT_TIME_SEC;
> For:msdos_rmdir()
> inode->i_ctime = CURRENT_TIME_SEC;
>
> b) For: vfat_unlink()
> inode->i_mtime = inode->i_atime = CURRENT_TIME_SEC;
> For: msdos_unlink()
> inode->i_ctime = CURRENT_TIME_SEC;
>
> So, atleast the uniformity in the code is missing for MSDOS and VFAT.
MSDOS doesn't have atime.
> 2) Regarding timings information
> Original timings on VFAT:
> #> mkdir parent
> #> stat parent
> File type: directory
> I-node number: 30
> Mode: 40755 (octal)
> Link count: 2
> Ownership: UID=0 GID=0
> Preferred I/O block size: 4096 bytes
> File size: 4096 bytes
> Blocks allocated: 8
> Last status change: Thu Jan 1 00:01:29 2012
> Last file access: Thu Jan 1 00:01:29 2012
> Last file modification: Thu Jan 1 00:01:29 2012
[...]
> As can be seen from the 'stat' information - the timing information
> appears same for VFAT like EXT4/XFS after changes.
> Please let me know your opinion.
You have to think about compatibility with other FAT, not unix fs.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-11-15 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 13:57 [PATCH 2/3] fat: fix time updates for create and delete Namjae Jeon
2012-11-11 16:09 ` OGAWA Hirofumi
2012-11-12 6:37 ` Namjae Jeon
2012-11-12 7:57 ` OGAWA Hirofumi
2012-11-12 7:58 ` OGAWA Hirofumi
2012-11-12 9:12 ` Namjae Jeon
2012-11-12 9:21 ` OGAWA Hirofumi
2012-11-12 9:22 ` OGAWA Hirofumi
2012-11-15 7:02 ` Namjae Jeon
2012-11-15 7:18 ` OGAWA Hirofumi [this message]
2012-11-16 10:12 ` Namjae Jeon
2012-11-16 13:47 ` OGAWA Hirofumi
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=87txsr49m8.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=amit.sahrawat83@gmail.com \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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