summaryrefslogtreecommitdiff
path: root/source3/smbd/oplock_onefs.c
AgeCommit message (Collapse)AuthorFilesLines
2010-04-12Move to using 64-bit mid values in our internal open file database.Jeremy Allison1-7/+9
This will allow us to share logic much easier between SMB1 and SMB2 servers. Jeremy
2010-04-09Plumb SMB2 stubs into all the places we defer SMB1 operations.Jeremy Allison1-3/+1
Rename functions to be internally consistent. Next step is to cope queueing single (non-compounded) SMB2 requests to put some code inside the stubs. Jeremy.
2009-11-03s3: Remove debug_ctx()Volker Lendecke1-4/+4
smbd just crashed on me: In a debug message I called a routine preparing a string that itself used debug_ctx. The outer routine also used it after the inner routine had returned. It was still referencing the talloc context that the outer debug_ctx() had given us, which the inner DEBUG had already freed.
2009-07-24s3 onefs: Fix the onefs modules after the big refactoringTim Prouty1-12/+12
2009-07-20s3: Change fsp->fsp_name to be an smb_filename struct!Tim Prouty1-5/+6
2009-07-20s3 onefs oplocks: Replace static fstring with talloc'd dbg_ctx()Tim Prouty1-16/+16
2009-05-12s3 onefs: Self-contend level2 oplocks on BRLZack Kirsch1-1/+0
2009-04-06s3 onefs: Simplify level 2 oplock self-contentionTim Prouty1-74/+5
This removes all oplock dependence on locking.tdb
2009-02-23s3 OneFS: Fix a double free in an error pathTim Prouty1-3/+2
2009-02-09s3 OneFS: Add kernel oplocks implementationTim Prouty1-0/+798
A few functions in oplocks_onefs.c need to be accessed from the onefs vfs module. It would be ideal if oplocks were implemented at the vfs layer, but since they aren't yet, a new header is added to source3/include to make these functions available to the onefs vfs module. oplocks_onefs.o doesn't need to be linked into the onefs vfs module explicitly, since it is already linked into smbd by default.