summaryrefslogtreecommitdiffstats
path: root/source/smbd/notify.c
Commit message (Collapse)AuthorAgeFilesLines
* Add some debug to notifyVolker Lendecke2008-06-171-0/+6
|
* Cleanup size_t return values in convert_string_allocateTim Prouty2008-04-111-4/+3
| | | | | This patch is the first iteration of an inside-out conversion to cleanup functions in charcnv.c returning size_t == -1 to indicate failure.
* Coverity fixesMarc VanHeyningen2008-03-171-1/+1
|
* Fix CID 505 - don't copy uninitialized memory.Jeremy Allison2008-01-111-0/+1
| | | | Jeremy.
* ensure uni_name.buffer is initialisedJeremy Allison2008-01-081-0/+2
| | | | | | merge from http://samba.org/~tridge/3_0-ctdb Jeremy.
* Refactor the crypto code after a very helpful conversationJeremy Allison2008-01-041-20/+26
| | | | | | with Volker. Mostly making sure we have data on the incoming packet type, not stored in the smb header. Jeremy.
* Add SMB encryption. Still fixing client decrypt butJeremy Allison2007-12-261-1/+2
| | | | | negotiation works. Jeremy.
* Add new parameter, "min receivefile size" (by default setJeremy Allison2007-10-301-1/+1
| | | | | | | | | to zero). If non-zero, writeX calls greater than this value will be left in the socket buffer for later handling with recvfile (or userspace equivalent). Definition of recvfile for your system is left as an exercise for the reader (I'm working on getting splice working :-). Jeremy.
* RIP BOOL. Convert BOOL -> bool. I found a few interestingJeremy Allison2007-10-181-4/+4
| | | | | | | bugs in various places whilst doing this (places that assumed BOOL == int). I also need to fix the Samba4 pidl generation (next checkin). Jeremy.
* [GLUE] Rsync SAMBA_3_2_0 SVN r25598 in order to create the v3-2-test branch.samba-misc-tags/initial-v3-2-testGerald (Jerry) Carter2007-10-101-4/+3
|
* r24809: Consolidate the use of temporary talloc contexts.Volker Lendecke2007-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the two functions talloc_stackframe() and talloc_tos(). * When a new talloc stackframe is allocated with talloc_stackframe(), then * the TALLOC_CTX returned with talloc_tos() is reset to that new * frame. Whenever that stack frame is TALLOC_FREE()'ed, then the reverse * happens: The previous talloc_tos() is restored. * * This API is designed to be robust in the sense that if someone forgets to * TALLOC_FREE() a stackframe, then the next outer one correctly cleans up and * resets the talloc_tos(). The original motivation for this patch was to get rid of the sid_string_static & friends buffers. Explicitly passing talloc context everywhere clutters code too much for my taste, so an implicit talloc_tos() is introduced here. Many of these static buffers are replaced by a single static pointer. The intended use would thus be that low-level functions can rather freely push stuff to talloc_tos, the upper layers clean up by freeing the stackframe. The more of these stackframes are used and correctly freed the more exact the memory cleanup happens. This patch removes the main_loop_talloc_ctx, tmp_talloc_ctx and lp_talloc_ctx (did I forget any?) So, never do a tmp_ctx = talloc_init("foo"); anymore, instead, use tmp_ctx = talloc_stackframe() :-) Volker
* r24512: Fix RAW-NOTIFYVolker Lendecke2007-10-101-2/+10
| | | | | With the inbuf consistency checks we have to more correctly fake the inbuf
* r24400: Fix a valgrind bugVolker Lendecke2007-10-101-2/+4
|
* r24399: Change change_notify_reply to use send_nt_replies_newVolker Lendecke2007-10-101-11/+6
|
* r24398: Convert call_nt_transact_notify_change to the new APIVolker Lendecke2007-10-101-8/+8
|
* r24314: Attempt to fix bug 4868Volker Lendecke2007-10-101-0/+1
|
* r23941: Don't use "False" when you mean "MARSHALL".Jeremy Allison2007-10-101-1/+1
| | | | Jeremy.
* r23940: Added missing line that was deleted accidently.Jeremy Allison2007-10-101-0/+2
| | | | | Should fix the build. Jeremy.
* r23939: Fixes for notify returns. Returned param value must fix insideJeremy Allison2007-10-101-19/+17
| | | | | max_param or return NT_STATUS_OK. Jeremy.
* r23784: use the GPLv3 boilerplate as recommended by the FSF and the license textAndrew Tridgell2007-10-101-2/+1
|
* r23779: Change from v2 or later to v3 or later.Jeremy Allison2007-10-101-1/+1
| | | | Jeremy.
* r23735: Second part of the bugfix for #4763Jeremy Allison2007-10-101-1/+21
| | | | | | This should coalesce identical adjacent notify records - making the "too large" bug very rare indeed. Please test. Jeremy.
* r23728: First part of bugfix for #4763. Limit notify responsesJeremy Allison2007-10-101-0/+12
| | | | | to client max buf size. Jeremy.
* r23518: Remove the silly assumption that string_replace requires a pstring.Volker Lendecke2007-10-101-5/+5
| | | | | | | | Jeremy, I am always very confused about the different length arguments in convert_string and friends. Can you take a look at the change in string_replace and verify it's ok? Thanks! While at it, remove the pstring limit for strhasupper and strhaslower.
* r23510: Tidy calls to smb_panic by removing trailing newlines. Print theJames Peach2007-10-101-1/+1
| | | | failed expression in SMB_ASSERT.
* r23450: max_params_return is complete fiction when getting a changenotifyJeremy Allison2007-10-101-14/+4
| | | | | | request. Ignore it. Should fix bug #4689 but more tests and valgrinding will follow. Jeremy.
* r22755: Second half of r22754. As it stands now, string_replace expects aVolker Lendecke2007-10-101-10/+8
| | | | | | pstring. Give it one, although I hate putting it in :-) Thanks to Tom Bork! :-)
* r22391: Looks bigger than it is. Make "inbuf" availableJeremy Allison2007-10-101-2/+3
| | | | | | | to all callers of smb_setlen (via set_message() calls). This will allow the server to reflect back the correct encryption context. Jeremy.
* r21123: Make notify_fsp() static to notify.c.Volker Lendecke2007-10-101-14/+68
| | | | Volker
* r21108: Send sys_notify_watch through the VFS, FAM is nextVolker Lendecke2007-10-101-6/+4
|
* r21093: Remove the hash and dnotify backends. Disabling FAM for this ↵Volker Lendecke2007-10-101-204/+0
| | | | | | | | checkin, I'm working on that right now. Volker
* r21092: Ok, that's the one that activates the Samba4 notify backend.Volker Lendecke2007-10-101-40/+57
| | | | | | Now to clean up / fix lots of stuff. Volker
* r21091: Fix the build without inotifyVolker Lendecke2007-10-101-0/+4
|
* r21090: Add some helper routinesVolker Lendecke2007-10-101-0/+38
|
* r21087: Make the param list of notify_fname match notify_triggerVolker Lendecke2007-10-101-2/+2
|
* r21084: Make the Samba4 files compile in Samba3, not activated yet.Volker Lendecke2007-10-101-0/+27
| | | | Volker
* r21077: A step to minimize the diff later: This pulls in unmodified files ↵Volker Lendecke2007-10-101-5/+0
| | | | | | | | | | | | | from Samba4, not compiled yet. This way the modifications become visible later. ntvfs/common/notify.c -> smbd/notify_internal.c ntvfs/sysdep/inotify.c -> smbd/notify_inotify.c Naturally I had to disable notify again :-) Volker
* r21064: The core of this patch isVolker Lendecke2007-10-101-2/+3
| | | | | | | | | | | | | | | | | | | | | | void message_register(int msg_type, void (*fn)(int msg_type, struct process_id pid, - void *buf, size_t len)) + void *buf, size_t len, + void *private_data), + void *private_data) { struct dispatch_fns *dfn; So this adds a (so far unused) private pointer that is passed from message_register to the message handler. A prerequisite to implement a tiny samba4-API compatible wrapper around our messaging system. That itself is necessary for the Samba4 notify system. Yes, I know, I could import the whole Samba4 messaging system, but I want to do it step by step and I think getting notify in is more important in this step. Volker
* r20982: Fix a segfault -- I wonder why my make test did not show this earlier...Volker Lendecke2007-10-101-1/+2
|
* r20932: This is the basic infrastructure for inotify support. This is far ↵Volker Lendecke2007-10-101-0/+5
| | | | | | | | | from being complete, in particular the various mask bits are not correctly supported yet. Checkin in now, I want to see how the build farm likes it. Volker
* r20931: This changes the notify infrastructure from a polling-based to an ↵Volker Lendecke2007-10-101-178/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | event-driven based approach. The only remaining hook into the backend is now void *(*notify_add)(TALLOC_CTX *mem_ctx, struct event_context *event_ctx, files_struct *fsp, uint32 *filter); (Should we put this through the VFS, so that others can more easily plug in?) The trick here is that the backend can pick filter bits that the main smbd should not handle anymore. Thanks to tridge for this idea. The backend can notify the main smbd process via void notify_fsp(files_struct *fsp, uint32 action, char *name); The core patch is not big, what makes this more than 1800 lines are the individual backends that are considerably changed but can be reviewed one by one. Based on this I'll continue with inotify now. Volker
* r20858: change_notify_reply_packet is staticVolker Lendecke2007-10-101-2/+4
|
* r20856: Make "struct notify_mid_map" private to notify.cVolker Lendecke2007-10-101-0/+11
|
* r20854: Ok, now I think we're at a point where looking at notify starts to ↵Volker Lendecke2007-10-101-28/+439
| | | | | | | | make sense again :-) Volker
* r20634: A *LOT* more work is necessary before touching notify remotely ↵Volker Lendecke2007-10-101-439/+28
| | | | | | | | | starts to make sense. Until then, remove it from the tree to keep the diff between 3_0_24 and 3_0 small. Volker
* r20602: Fix coverity ID 339. SMB_ASSERT does not panic without -DDEVELOPER.Volker Lendecke2007-10-101-1/+4
| | | | Volker
* r20597: Survive some of the notify mask tests.Volker Lendecke2007-10-101-0/+14
|
* r20451: Survive the first of the filter-tests (mkdir).Volker Lendecke2007-10-101-16/+24
| | | | | | Add lots of TODOs :-) Volker
* r20443: Fix a compiler warningVolker Lendecke2007-10-101-1/+2
|
* r20442: Slight rewrite of the change notify infrastructure. This now ↵Volker Lendecke2007-10-101-66/+136
| | | | | | | | | | | | | | | | | | | | | | | | survives the first of the raw-notify subtests, the one-level test_notify_dir without any flags around yet. The tricky part was getting the data structures right, I hope the next tests don't let that fall over. fsp->notify is now by default NULL, meaning that nobody has issued a changenotify call. This means nobody is interested in changes for this directory. If that has happened, notify_change_buf collects the changes if no current request is outstanding, and it collects the requests if no change has happened since the last request. Happy New Year, somewhere on this planet it's already 2007 :-) Volker P.S: Jeremy, there's a question for you in smbd/files.c line 367.
generated by cgit (git 2.34.1) at 2025-09-04 09:27:37 +0000