s3:vfs_tsmsm only send notifications when file was offline before Autobuild-User(master): Christian Ambach <ambi@samba.org> Autobuild-Date(master): Fri Aug 17 20:05:30 CEST 2012 on sn-devel-104
s3: Adapt the tsmsm module to the new aio routines Signed-off-by: Christian Ambach <ambi@samba.org>
s3-vfs: Fix calls of lp_parm_talloc_string Signed-off-by: Christian Ambach <ambi@samba.org>
build: Remove SMB_OFF_T, replace with off_t Now that we always require a 64 bit off_t, we no longer need SMB_OFF_T. Andrew Bartlett Autobuild-User: Andrew Bartlett <abartlet@samba.org> Autobuild-Date: Fri Apr 6 01:47:43 CEST 2012 on sn-devel-104
s3:vfs_tsmsm: Fix a misspelling of a config parameter in the doc-comment The module uses "tsmsm:dmapi attribute" instead of "tsmsm:attribute name".
vfs: Make function pointer names consistent. They all end in _fn Autobuild-User: Richard Sharpe <sharpe@samba.org> Autobuild-Date: Mon Dec 12 04:58:40 CET 2011 on sn-devel-104
s3-talloc Change TALLOC_ZERO_P() to talloc_zero() Using the standard macro makes it easier to move code into common, as TALLOC_ZERO_P isn't standard talloc.
s3-vfs: include smbd/smbd.h in vfs modules. Guenther
s3: Pass smb_filename through the set_offline vfs op
s3: Pass smb_filename through the is_offline vfs op
s3/vfs_tsmsm: remove unneeded cast to off_t "off_t" is wrong on 32 bit systems anyhow ... Autobuild-User: Björn Jacke <bj@sernet.de> Autobuild-Date: Thu Nov 18 14:47:59 UTC 2010 on sn-devel-104
s3/vfs_tsmsm: fix debug output for large files
Restructure the connect function code to always call down to NEXT-> before initializing. This allows us to do cleanup (by calling DISCONNECT) if initialization fails. Also fix vfs_acl_xattr which was failing to call the NEXT connect function. Jeremy.
s3:vfs: Fix the build of vfs_tsmsm after the VFS rewrite
Second attempt at fix for bug 6529 - Offline files conflict with Vista and Office 2003. Confirmation from reporter that this fixes the issue in master on ext3/ext4. Back-ports to follow. Jeremy.
Fix breakage for connect function after API change (connect -> connect_fn)
Make the smbd VFS typesafe
s3: Finish plumbing the fsp->fsp_name smb_fname conversion through the modules.
Introduce "struct stat_ex" as a replacement for SMB_STRUCT_STAT This patch introduces struct stat_ex { dev_t st_ex_dev; ino_t st_ex_ino; mode_t st_ex_mode; nlink_t st_ex_nlink; uid_t st_ex_uid; gid_t st_ex_gid; dev_t st_ex_rdev; off_t st_ex_size; struct timespec st_ex_atime; struct timespec st_ex_mtime; struct timespec st_ex_ctime; struct timespec st_ex_btime; /* birthtime */ blksize_t st_ex_blksize; blkcnt_t st_ex_blocks; }; typedef struct stat_ex SMB_STRUCT_STAT; It is really large because due to the friendly libc headers playing macro tricks with fields like st_ino, so I renamed them to st_ex_xxx. Why this change? To support birthtime, we already have quite a few #ifdef's at places where it does not really belong. With a stat struct that we control, we can consolidate the nanosecond timestamps and the birthtime deep in the VFS stat calls. At this moment it is triggered by a request to support the birthtime field for GPFS. GPFS does not extend the system level struct stat, but instead has a separate call that gets us the additional information beyond posix. Without being able to do that within the VFS stat calls, that support would have to be scattered around the main smbd code. It will very likely break all the onefs modules, but I think the changes will be reasonably easy to do.
s3:vfs_tsmsm: fix potential segfault (freeing uninitialized buffer) Michael