Date: Wed, 02 May 2018 03:59:07 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 111843] [msdosfs] Long Names of files are incorrectly created on msdosfs Message-ID: <bug-111843-227-E6QwOMxw2X@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-111843-227@https.bugs.freebsd.org/bugzilla/> References: <bug-111843-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=111843 --- Comment #6 from Damjan Jovanovic <damjan.jov@gmail.com> --- That wasn't the commit in which NetBSD first fixed this bug. Their code was correct from the start - the 1995 commit that added long filenames uses decrementing unlen to detect end of filename instead of equality with '\0': https://github.com/NetBSD/src/commit/e0c5bef42599b40c241b8a09e6ac9c56b6246b3a But yes, the new code in unix2winfn() in the commit you found would also fix this bug, though yet another approach, that detects end of the filename by comparing this LFN entry's offset into the full filename against its space/dot-trimmed length. What now? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-111843-227-E6QwOMxw2X>