When adding "vfs objects = acl_tdb" to the smb.conf, creating new files on a Samba share leads to smbd segfaults.
smb.conf: [global] workgroup = SAMBA security = user log level = 10 max log size = 0 debug pid = yes debug hires timestamp = yes log file = /var/log/samba/log.%I vfs objects = acl_tdb [tmp] path = /tmp writeable = yes [test] path = /data/samba/test writeable = yes
Created attachment 5526 [details] smbd log file
Error message: Service no longer available. Two files will be created (usually, sometimes only one). bando:/tmp # ls -al /data/samba/test/ insgesamt 8 drwxrwxrwx 2 root root 4096 23. Mär 16:57 . drwxrwxrwx 3 root users 4096 23. Mär 15:18 .. -rwxr-xr-x 1 kseeger users 0 23. Mär 16:52 Neu Bitmap (2).bmp -rwxr-xr-x 1 kseeger users 0 23. Mär 16:52 Neu Bitmap.bmp
Cannot add valgrind output due to Bugzilla error messages. Can send it directly if needed.
Reproduceable with current v3-5-test branch also.
Ok, I understand this. Patch to follow. Jeremy.
Created attachment 5533 [details] Fix for 3.5.2.
Karolin please test and apply if this fixes the problem for you. I will apply to master. Jeremy.
(In reply to comment #8) > Karolin please test and apply if this fixes the problem for you. I will apply > to master. > > Jeremy. > Yes, your patch fixes the issue on my box! :-) Thanks a lot, Jeremy!
Comment on attachment 5533 [details] Fix for 3.5.2. why the change in posix_acls.c? why is the same tdb used by each share?
Oh, I didn't notice the posix_acls.c change. It fixes a valgrind error where it's complaining about src and dest beign identical in this assignment. The same tdb is just the original design (by vl). Jeremy.
Comment on attachment 5533 [details] Fix for 3.5.2. Looks ok to me
Pushed patch to v3-5-test. Closing out bug report. Thanks!