smbfs and failed nls translations

smbfs and failed nls translations

[Grover, Andrew]

[resending - fingers instinctually typed wrong lkml address last time]

<urban@teststation.com> (02/03/07 1.375.1.137)
	[PATCH] smbfs nls oops fix
	
	Fixes smbfs oopsing on failed nls translations and maps unknown
chars to
	:#### strings. Also PATHLEN vs NAMELEN mixups.

Hi, apparently my smbfs mounts have had failed nls translations, but I
didn't know it -- never saw any warnings. So when I upgraded to 2.5.6 that
included this patch, the filenames on my samba mounts all turned into
"x00:x00..." etc. ;-)

Turning off CONFIG_SMB_NLS_DEFAULT produces a different, but still failing,
result.

How can I get samba working again? What am I doing wrong? And, why is samba
so stingy with the error messages in this case?

Thanks -- Regards -- Andy

----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover@intel.com



----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover@intel.com

Re: smbfs and failed nls translations

[Urban Widmark]

On Mon, 11 Mar 2002, Grover, Andrew wrote:

> Hi, apparently my smbfs mounts have had failed nls translations, but I
> didn't know it -- never saw any warnings. So when I upgraded to 2.5.6 that
> included this patch, the filenames on my samba mounts all turned into
> "x00:x00..." etc. ;-)

smbmount from certain samba versions always negotiate unicode support.
smbfs should probably turn on it's internal unicode support when it sees
that, but right now it doesn't.

samba 2.2.1 is known to error this way, 2.2.3 should be fixed.

One workaround should be to pass codepage=unicode or to specify unicode as
the CONFIG_SMB_NLS_DEFAULT. Another to upgrade samba.

Please post the exact output of a few filenames as well as the expected
names if none of the above helps.

/Urban