bug#24656: 25.1; Emacs leaves lock files on a CIFS share

[Jan Synacek]

On Mon, Oct 10, 2016 at 2:14 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: jsynacek@redhat.com (Jan Synáček)
>> Date: Mon, 10 Oct 2016 13:30:24 +0200
>>
>> # ls -la /mnt/tmp/
>> total 9
>> drwxrwxrwx+ 2 root      root       0 Oct 10 13:21 .
>> drwxr-xr-x. 1 root      root      20 Jul 15 10:33 ..
>> lrwxrwxrwx. 1 nfsnobody nfsnobody 54 Oct 10 13:21 .#test.txt -> 
>> jsynacek@jsynacek-ntb.brq.redhat.com.57671476081527
>> -rw-rw-rw-+ 1 jsynacek  users     10 Oct 10 13:16 test.txt
>>
>> When I save the file and quit emacs, the lock file stays there. It
>> should be removed. Maybe it's because of the weird 0xF022 sequence in
>> the file name?
>
> That 0xF022 should have been a colon ':'.
>
> Can you step with a debugger through lock_file_1 and see how this file
> name happens to come up?  Is it possible that Samba doesn't allow the
> colon characters in its file names, and the network re-director
> replaces the colon with that strange character?  If so, would using a
> different character, like comma, fix the problem?
>
> Thanks.

The lock_file_1 correctly uses a path with a colon in it. Indeed,
samba seems to substitute it. I tried to patch the emacs source to use
a comma instead. It didn't get substituted by samba, but the lock file
didn't go away when I exited emacs.

-- 
Jan Synacek
Software Engineer, Red Hat