From owner-freebsd-current@FreeBSD.ORG Tue Dec 16 03:49:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75ADE16A4CE; Tue, 16 Dec 2003 03:49:45 -0800 (PST) Received: from smtp02.syd.iprimus.net.au (smtp02.syd.iprimus.net.au [210.50.76.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8C4043D31; Tue, 16 Dec 2003 03:49:43 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.203.147) by smtp02.syd.iprimus.net.au (7.0.020) id 3F8F522A013D08B3; Tue, 16 Dec 2003 22:49:42 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id F36F66110; Tue, 16 Dec 2003 22:50:01 +1100 (EST) Date: Tue, 16 Dec 2003 22:50:01 +1100 From: Tim Robbins To: Alexander Zagrebin Message-ID: <20031216115001.GA6913@wombat.robbins.dropbear.id.au> References: <200312121243.11908.alexz@visp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312121243.11908.alexz@visp.ru> User-Agent: Mutt/1.4.1i cc: fjoe@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: RELENG_5_2 ntfs mounting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2003 11:49:45 -0000 On Fri, Dec 12, 2003 at 12:43:11PM +0300, Alexander Zagrebin wrote: > Hi! > > The FreeBSD 5.2-RC has problem with russian (cyrillic) file names on NTFS > volumes. > If the file name is "????" (hex: 0xd4 0xc5 0xd3 0xd4), then after mounting its > name looks like 0xff 0xd4 0xff 0xc5 0xff 0xd3 0xff 0xd4, so file is > inaccessible. > I reason is in function "wchar ntfs_u28" (file ntfs_subr.c). > This function returns value of outbuf (char), converted to wchar. The highest > bit of russian characters (koi8-r encoding) is always 1, so this conversion > works incorrectly (data type char is signed). Thanks for the report. This has been fixed in -current. I'll try to get it committed to RELENG_5_2 before the release if possible. Tim