Re: kern/50608 (udf fails the fs/vfs/t_vnops::create_many test)

[Reinoud Zandijk <reinoud%NetBSD.org@localhost>]

The following reply was made to PR kern/50608; it has been noted by GNATS.

From: Reinoud Zandijk <reinoud%NetBSD.org@localhost>
To: Andreas Gustafsson <gson%gson.org@localhost>
Cc: pooka%NetBSD.org@localhost, gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/50608 (udf fails the fs/vfs/t_vnops::create_many test)
Date: Wed, 13 Jan 2016 20:17:52 +0100

 On Wed, Jan 13, 2016 at 08:34:49PM +0200, Andreas Gustafsson wrote:
 > I'm considering removing the newlines from the create_many test and instead
 > adding a separate test of files with non-alphanumeric characters in their
 > names.
 
 It had a newline in the name?? Since when is this allowed?
 
 > Running t_vnops in the debugger, I see that for the filename "testfile0\n",
 > udf_to_unix_name() is returning the string "testfile0_#2A44".  The file is
 > not found because those two strings are not the same.
 
 Thats how it is supposed to work in UDF; names are transcribed to and from
 compressed unicode-16 in a standard prescribed way. This '\n' is seen as an
 illegal character and replaced by a _ but to avoid aliases its appended with
 '#' and a kind of checksum/crc character.
 
 Is the code also trying to delete the files with names appened with '\n'?
 Either this or some rump code is removing the '\n' in the remove code. If it
 would pass the filename exactly the same I see no reason it should not have
 found it. Last time I tested the regression test on names, all passed. They
 also explicitly test for mangled filenames and UTF support.
 
 Reinoud