Upstream reports this is resolved in the kernel client in Linux 2.6.29
and above; marking fixed here.
** Package changed: samba (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
Default ACL not applied on files created through CIFS filesystem (mo
** Changed in: samba
Status: Confirmed => Fix Released
--
Default ACL not applied on files created through CIFS filesystem (mount.cifs)
https://bugs.launchpad.net/bugs/271922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Marking this as triaged since it was sent upstream at
https://bugzilla.samba.org/show_bug.cgi?id=5807 ; thanks all.
** Changed in: samba (Ubuntu)
Importance: Undecided => Low
Status: New => Triaged
--
Default ACL not applied on files created through CIFS filesystem (mount.cifs)
https:/
I can confirm the default ACL for other are being applied correctly on
file creation through a CIFS mount with the POSIX extensions disabled,
on hardy.
The ability to create pipe and socket is not important in my case, and I
think I can do without POSIX file locking. As such, disabling the POSIX
Hi Michael,
In the case of Ubuntu 8.10, I think this is principally an oversight.
Note, however, that I've also tested this behavior with the jaunty
kernel which does have CIFS_POSIX_XATTR set, and it makes no difference
to this bug because of the atomicity issue I've outlined.
--
Default ACL no
I was looking for a reason why Ubuntu kernels dont have CIFS_POSIX_XATTR set?
So the nifty posix acl extensions can never be used with stock kernel.
Should we open a new enhancement bug report for this or was I just not clever
enough searching...
Michael
--
Default ACL not applied on files crea
And the mode being requested by the client is mediated by the umask.
A full fix for this will require the client to set the mode atomically
at file creation time, at a point where the samba server can apply the
mode in the open call instead of as a separate chmod() call. The
NTCreateAndXRequest R
Correction; the perms are being set on request of the client:
[2009/01/24 13:50:41, 5] smbd/filename.c:unix_convert(290)
conversion finished test-acl/file-cifs -> test-acl/file-cifs
[2009/01/24 13:50:41, 3] smbd/trans2.c:call_trans2setfilepathinfo(6702)
call_trans2setfilepathinfo(6) test-acl
Disabling Unix CIFS extensions with 'echo 0 >
/proc/fs/cifs/LinuxExtensionsEnabled', the kernel cifs client now works
for me (tested with the current jaunty kernel). Attached is a network
trace showing the same operation ('touch file-cifs') with POSIX
extensions disabled; the SET_FILE_INFO level i
There's definitely a client difference here. When smbclient connects,
it makes a single OpenAndX request; the kernel cifs client instead calls
NTCreateAndX, followed by two SET_PATH_INFO Trans2 requests. The
SET_PATH_INFO is probably what's clobbering the ACL.
Partial network trace showing the c
** Changed in: samba
Status: Unknown => Confirmed
--
Default ACL not applied on files created through CIFS filesystem (mount.cifs)
https://bugs.launchpad.net/bugs/271922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubunt
However, on Intrepid when using the upstream 3.3.0pre2 from source, file
do not inherit default ACL for "other" even when the file is created
using smbclient.
I should also note that using an ACL for a named group instead of
"other" (ie, setfacl -m d:g:users:rwx) work as expected in all test
cases
Just tried using the latest upstream source (3.3.0pre2) on the server
side with Intrepid, and it fail too. I will report to Samba Bugzilla,
and see what they have to say.
--
Default ACL not applied on files created through CIFS filesystem (mount.cifs)
https://bugs.launchpad.net/bugs/271922
You r
Just tested on Intrepid (both client and server), and I get the same
behavior: directory created through the CIFS mounted file system inherit
the default ACL correctly but files do not, while it work as expected
when creating either directory or file using smbclient.
--
Default ACL not applied on
The problem could be on the server side. I just tested with Ubuntu
7.10, with the old smbmount and smb kernel module, and the behavior is
the same as when using mount.cifs and the cifs kernel module: directory
inherit ACL fine, but not files.
--
Default ACL not applied on files created through C
** Description changed:
Binary package hint: smbfs
When creating files on a CIFS-mounted filesystem, default ACL are not
inherited. However, directory created on same CIFS-mounted filesystem
works just fine.
Both server and client are Ubuntu 8.04. On the server, running samba
3
** Description changed:
Binary package hint: smbfs
When creating files on a CIFS-mounted filesystem, default ACL are not
inherited. However, directory created on same CIFS-mounted filesystem
works just fine.
Both server and client are Ubuntu 8.04. On the server, running samba
3
17 matches
Mail list logo