Opened on 02/14/09 at 06:56:29
Closed on 05/15/10 at 06:48:49
#1379 closed defect (wontfix)
msdos_filename_unix2dos sets \x0 in name
Reported by: | Chris Johns | Owned by: | Joel Sherrill |
---|---|---|---|
Priority: | normal | Milestone: | 4.10 |
Component: | fs | Version: | 4.10 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
The DOSFS does not allow a \0x (nul) character in a file name. If a Unix file name has a character that is mapped to \0x the code currently places the \0x in the DOS file name. This is an error and detected by the dosfsck program.
Change History (1)
comment:1 Changed on 05/15/10 at 06:48:49 by Chris Johns
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I cannot see the problem in the DOSFS code. If an trace can so the failure other than the dosfsck then I will take a look.