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

[Andreas Gustafsson <gson%gson.org@localhost>]

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

From: Andreas Gustafsson <gson%gson.org@localhost>
To: Reinoud Zandijk <reinoud%NetBSD.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:34:49 +0200

 Reinoud Zandijk wrote:
 > I've tried your sequence and indeed it fails on an physical amd64. What I
 > meant is that i tried out a program that does exactly the same as the test
 > only then *without* RUMP and that passes fine.
 > 
 > I'll try to dig into the issue, might be the generic dirhash code misbehaving
 > though i still think its a rump internal problem.
 
 In your test, does the filename contain an embedded newline character
 like the ones in t_vnops do?  For example, the first file in the test
 is actually called "testfile0\n", not "testfile0".  This looks like a
 bug in the test (hi pooka!), but it's a useful bug if it is also
 exposing a bug in udf.  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.
 
 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.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost