This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001193] abnormal behavior readdir on fat16
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Mon, 15 Apr 2013 17:57:53 +0000
- Subject: [Bug 1001193] abnormal behavior readdir on fat16
- Auto-submitted: auto-generated
- References: <bug-1001193-777 at http dot bugs dot ecos dot sourceware dot org/>
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001193
Mike Jones <mjones@linear.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjones@linear.com
--- Comment #1 from Mike Jones <mjones@linear.com> ---
I am seeing this same behavior. In the process of debugging, I noticed the
FAT16/FAT32 discovery during mount uses number of clusters and not an
attribute. This means that if I format the SD on Linux, it believes it is
FAT16, and if I format the SD on DOS, it thinks it is FAT32. Neither change the
results that give me the extra directories.
The detected attribute of the directory is 0xF. That means a hidden read only
system file. No such files show up when the SD is mounted on DOS or Linux. The
cluster is 0 and file size -1.
I believe this means it is the directory '..'
Not being an expert about FAT, it seems unusual to find more than one of these
in the root dir. Perhaps it has something to do with how the table is searched
where it goes into a dir, finds this, and goes back up. If so, perhaps the code
should filter out the '..'.
--
You are receiving this mail because:
You are the assignee for the bug.