Re: msdosfs and cd9660: stat(2) returns garbled birthtime
- From: Oliver Fromme <olli@xxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Dec 2006 16:45:40 +0100 (CET)
Ulrich Spoerlein wrote:
at least msdosfs and cd9660 do not fill the birthtime for the stat(2)
syscall. Thus stat(1) will return different values per call:
[...]
The code in cd9660_getattr() and msdosfs_getattr() should be
augmented. But what value to put into the field? Clearly, a constant
would be preferred instead of an uninitialized value.
Please see PR kern/106018. It fixes the msdosfs case;
it has already been committed a few weeks ago.
I haven't looked at the cd9660 code, but if you see
similar problems there, then I guess it needs a similar
fix. ;-)
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
"C++ is the only current language making COBOL look good."
-- Bertrand Meyer
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: msdosfs and cd9660: stat(2) returns garbled birthtime
- From: Ulrich Spoerlein
- Re: msdosfs and cd9660: stat(2) returns garbled birthtime
- References:
- msdosfs and cd9660: stat(2) returns garbled birthtime
- From: Ulrich Spoerlein
- msdosfs and cd9660: stat(2) returns garbled birthtime
- Prev by Date: FreeBSD 7.0 i386 via cvsup failed in buildkernel
- Next by Date: Re: msdosfs and cd9660: stat(2) returns garbled birthtime
- Previous by thread: msdosfs and cd9660: stat(2) returns garbled birthtime
- Next by thread: Re: msdosfs and cd9660: stat(2) returns garbled birthtime
- Index(es):