samba - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2009-03-13	s3 OneFS: Add kernel strict locking support	Dave Richards	1	-0/+4

2009-03-03	s3 OneFS: Add parameter to ignore streams	Tim Prouty	1	-1/+8

2009-03-01	s3 OneFS: Refactor config code and cleanup includes	Tim Prouty	1	-200/+1

2009-02-25	s3 OneFS: Add .snapshot directory configuration handling	Tim Prouty	1	-23/+121

2009-02-21	s3 OneFS: Add an atomic sendfile implementation	Tim Prouty	1	-0/+15

2009-02-20	s3: OneFS implementation of change notify	Steven Danneman	1	-0/+2
	The OneFS Samba implementation of change notify is modeled after the usage of Linux's inotify kernel subsystem. A single call is made into the onefs.so VFS module to initialize kernel tracking of certain file change events. When these events occur a kernel notification is sent to smbd and the notification event is translated and given to the general Samba Change Notify layer through a callback function. The most difficult aspect is converting an SMB CompletionFilter to a matching ifs_event mask, and then back to an appropriate change notify action. Currently, not all possible cases are handled by the this module, but the most prevalent ones, which are tested by smbtorture, are implemented.
2009-02-19	s3 OneFS: Add file_id_create implementation to take advantage of snapshots	Tim Prouty	1	-0/+18

2009-02-16	s3 OneFS: Add defaults to the fake timestamp parameters	Tim Prouty	1	-8/+11

2009-02-13	s3 OneFS: Add recvfile implementation	Tim Prouty	1	-0/+14

2009-02-13	s3 OneFS: Add vfs implementation for SMB_VFS_GET_REAL_FILE_NAME	Aravind Srinivasan	1	-0/+41

2009-02-13	OneFS implementation of BRL VFS ops:	Zack Kirsch	1	-0/+6
	* Much of the beginning should look familiar, as I re-used the OneFS oplock callback record concept. This was necessary to keep our own state around - it really only consists of a lock state, per asynchronous lock that is currently unsatisfied. The onefs_cbrl_callback_records map to BLRs by the id. * There are 4 states an async lock can be in. NONE means there is no async currently out for the lock, as opposed to ASYNC. DONE means we've locked every lock (keep in mind a request can ask for multiple locks at a time.) ERROR is an error. * onefs_cbrl_async_success: The lock_num is incremented, and the state changed, so that when process_blocking_lock_queue is run, we will try the next lock, rather than the same one again. * onefs_brl_lock_windows() has some complicated logic: * We do a no-op if we're passed a BLR and the matching state is ASYNC -- this means Samba is trying to get the same lock twice, and we just need to wait longer, so we return an error. * PENDING lock calls happen when the lock is being queued on the BLQ -- we do async in this case. * We also do async in the case that we're passed a BLR, but the lock is not pending. This is an async lock being probed by process_blocking_lock_queue. * We do a sync lock for any normal first request of a lock. * Failure is returned, but it doesn't go to the client unless the lock has actually timed out.
2009-02-09	s3: OneFS bulk directory enumeration support	Steven Danneman	1	-4/+20
	OneFS provides the bulk directory enumeration syscall readdirplus(). This syscall has the same semantics as the NFSv3 READDIRPLUS command, returning a batch of directory entries with prefetched stat information via one syscall. This commit wraps the readdirplus() call in the existing POSIX readdir/seekdir VFS interface. By default a batch of 128 directory entries are optimistically read from the kernel into a global cache, and fed to iterative calls of VFS_OP_READDIR. The global buffers could be avoided in the future by hanging connection specific buffers off the conn struct. Added new parameter "onefs:use readdirplus" which toggles usage of this code on or off.
2009-02-09	s3 OneFS: Fake Timestamps	todd stecher	1	-0/+114
	This checkin enables setting arbitrary timestamps on files matching the pattern stored in smb.conf. This was a customer request for a specific workflow. Changes include: 1) configuration state machine to avoid tons of string comparisons on each and every stat. 2) Code to adjust post-stat() times to match time now, or sloptime + time now.
2009-01-29	s3 onefs: Add the OneFS implementation of SMB_VFS_GET_ALLOC_SIZE	Tim Prouty	1	-0/+27

2009-01-23	Modify OneFS module to support new NTIMES interfaces	todd stecher	1	-0/+35

2009-01-11	s3: Add OneFS alternate data streams implementation	Tim Prouty	1	-0/+23

2009-01-11	s3: General cleanup of the open path in the OneFS vfs module	Tim Prouty	1	-2/+4

2008-12-17	s3: Add statvfs implementation to the onefs vfs module	Aravind Srinivasan	1	-0/+28

2008-12-09	s3: Add the OneFS SMB_VFS_CREATE_FILE implementation	Tim Prouty	1	-7/+20
	This is the first pass at extending the onefs vfs module to support the CIFS-specific enhancements available on OneFS. Most of this patch is massaging the sama open path to work with ifs_createfile. ifs_createfile is a CIFS-specific syscall for opening/files and directories. It adds support for: - Full in-kernel access checks using a windows access_mask - Cluster-coherent share mode locks - Cluster-coherent oplocks - Streams - Setting security descriptors at create time - Setting dos_attributes at create time This patch does not implement the samba side of the streams support or oplocks support. Tests that expect oplocks to be granted or streams to be supported will fail. This will be remedied in upcoming patches.
2008-12-02	Add support for OneFS ACLs	Steven Danneman	1	-0/+15
	Add to the OneFS VFS module, support for NTFS ACLs through the calls: SMB_VFS_FGET_NT_ACL() SMB_VFS_GET_NT_ACL() SMB_VFS_FSET_NT_ACL() Also create several new onefs specific smb.conf parameters in onefs.h
2008-12-02	Add OneFS VFS module skeleton.	Tim Prouty	1	-0/+33
	Also set configure to autodetect OneFS OS and build this VFS module.