lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87txsr49m8.fsf@devron.myhome.or.jp>
Date:	Thu, 15 Nov 2012 16:18:39 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Namjae Jeon <linkinjeon@...il.com>
Cc:	akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Amit Sahrawat <amit.sahrawat83@...il.com>
Subject: Re: [PATCH 2/3] fat: fix time updates for create and delete

Namjae Jeon <linkinjeon@...il.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@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ