Per the source for Reiser or to get an answer, go to the Reiser Site at http://namesys.com or reiser@namesys.com I quit using Reiser as my successive SuSE release updates would not recognize the volumes and could not mount them. I would have to go to the Reiser Site, obtain the version that SuSE was using, then load and compile, then rebuild the file system. I just went to Ext3 --- not as criticism of Reiser. neither Reiser nor I could fathom why SuSE's installation would not provide a bridge for allowing for updating the Reiser file system with an upgrade. The folks at namesys.com, the owners of Reiser, are great and helpful. melissa

-----Original Message----- From: Guido Tschakert [mailto:guido.tschakert@src-gmbh.de] Sent: Tuesday, August 3, 2004 01:53 PM To: suse-security@suse.com Subject: Re: [suse-security] reiserfs strange behavior

Hello,

...

You may even try the following pairs bb3001/am3001 gb3001/fm3001 mb4001/lm4001 mb4002/lm4002 ma4001/ll4001 td3001/so3001 ma4001/ll4001

I found these files becaus this is my system for user accounts. Among my 1300 usernames I found about 10 pairs with this kind of clash!

I also can confirm the problem (didn't test the hole bunch written above :-) Is anybody here knowing the sourcecode of reiserfs (At the moment I don't have installed the source nor I have the time to look through). I wonder if this names are reserved in some way by reiserfs, so you can't use'm. I also tried to find a correaltion between the pairs mentioned above, but I didn't see anything :-(

...

But will this be the only ones?

I fear there are more of this kind. Why should it be only 7 pairs, you found by chance.

Somebody here who can test it on another Kernel < 2.6.5 In Kernel 2.4.x (no I did not test all of them :-) I didn't found the problem. I could imagine that it is a problem of kernel 2.6.x + reiserfs.

guido

...

Best Uwe

-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here