#490 closed defect (fixed)

uninitialized memory access in TahoeFS

Reported by: ghazel Owned by: booker
Priority: major Milestone: undecided
Component: code-frontend-w32 Version: 1.1.0
Keywords: Cc: ghazel
Launchpad Bug:

Description

http://allmydata.org/trac/tahoe-w32-client/browser/WinFUSE/TahoeFS/TahoeFS.cs#L1621

The DirectoryContext? member for LastWriteTime? (at least) is not initialized in that constructor.

This causes:

Z:\>dir
 Volume in drive Z is TahoeFS
 Volume Serial Number is 4996-02D2

 Directory of Z:\

The parameter is incorrect.
ë╙♠)    <DIR>          .
The parameter is incorrect.
ë╙♠)    <DIR>          ..
07/17/2008  08:08 PM    <DIR>          Backups
               0 File(s) 18,446,744,073,709,551,614 bytes
               3 Dir(s)  1,099,511,627,776 bytes free

instead of:

Z:\>dir
 Volume in drive Z is TahoeFS
 Volume Serial Number is 4996-02D2

 Directory of Z:\

07/16/2008  12:26 PM    <DIR>          .
07/16/2008  12:26 PM    <DIR>          ..
07/17/2008  08:08 PM    <DIR>          Backups
               0 File(s) 18,446,744,073,709,551,614 bytes
               3 Dir(s)  1,099,511,627,776 bytes free

Or somesuch. The uninitialized memory can in fact be a valid looking date and time, but the "The parameter is incorrect." message will still appear.

Change History (2)

comment:1 Changed at 2008-07-18T19:38:49Z by ghazel

  • Component changed from code-frontend to code-frontend-w32

comment:2 Changed at 2008-07-21T01:37:15Z by Michael Booker

  • Resolution set to fixed
  • Status changed from new to closed

last access time, last modified time, created time and size are all initilized properly for the "." and ".." directory link entries now.

Note: See TracTickets for help on using tickets.