>>>>generic bug in handling hash collisions? >>>> >>>> >>>Tea hash is designed to be more resistant. >>> >>> >> >>As the example posted shows, tea doesn't look better, it generates >>nicely-looking collisions, too. >> >> > You mean, in practice you hit them, or with an artificially generated > set of filenames intended to cause collisions you get those collisions?
Excuse me, but do you mean that there are undocumented limits on what files can be named to, and how many files with similar or random names in a ReiferFS volume? This sounds bad...
