public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001193] abnormal behavior readdir on fat16 Date: Mon, 15 Apr 2013 17:58:00 -0000 [thread overview] Message-ID: <bug-1001193-777-PYoToX7Jif@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001193-777@http.bugs.ecos.sourceware.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.
next prev parent reply other threads:[~2013-04-15 17:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-07 19:33 [Bug 1001193] New: " bugzilla-daemon 2013-04-15 17:58 ` bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-04-07 19:33 bugzilla-daemon 2013-04-15 17:58 ` [Bug 1001193] " bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001193-777-PYoToX7Jif@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).