Re: RFC: Change mtree nsec handling?

From: Poul-Henning Kamp <phk_at_phk.freebsd.dk>
Date: Fri, 30 Jan 2009 21:19:08 +0000
In message <20090130203033.GB52415_at_deviant.kiev.zoral.com.ua>, Kostik Belousov 
writes:

>> >>_at__at_ -258,6 +259,8 _at__at_
>> >>				val = ep + 1;
>> >>				ip->st_mtimespec.tv_nsec
>> >>				    = strtoul(val, &ep, 10);
>> >>+				for (i = ep - val; i < 9; ++i)
>> >>+					ip->st_mtimespec.tv_nsec *= 10;
>> >
>> >
>> >Why is this bit needed ?
>> >
>> 
>> This is the part that converts 1233295862.000001 into
>> 1000 nanoseconds (instead of 1 nanosecond).

But that wouldn't happen, because no mtree file has that
content.

Either it has 1233295862.000001000 from the new %09d
or it has 1233295862.1000 from the old %d

Please leave this out, it can only cause problems.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Fri Jan 30 2009 - 20:19:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:41 UTC