Alternate Data Stream bug in Samba 3.*

Volker Lendecke Volker.Lendecke at SerNet.DE
Fri Aug 29 09:31:44 GMT 2008

On Thu, Aug 28, 2008 at 09:07:58PM -0700, lipson wrote:
>         Today, I found a quite interesting problem on samba 3.2.1 with ext3
> as backend filesystem. I thought that could be a breakpoint for this bug. 
>         Bug reproduce steps:
>         1. export a ext3 filesystem with xattr support through samba 3.2.1 
>         2. On the server side, touch a file and setfattr as follows:
>             $> touch testfile
>             $> setfattr -n user.DosStream.whatever -v value testfile  //
> Note: be sure to set the attribute as pattern : user.DosStream.*
>             $> getfattr -d testfile           // check the file setting. 
>         3. Map a driver on Windows client, and DELETE the "testfile" file.  
>             // there you go, you would see a error message "cann't find the
> specified file...."
>         4. Things works well if the xattr pattern wasn't "user.DosStream.*".
> And that's the funny place and also a potential breakpoint for the bug. 

Tried exactly that with v3-devel, works for me. Can you try
3.2.3? Or send the valgrind log on an smbd compiled with -g?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the samba-technical mailing list