1
0
mirror of https://github.com/samba-team/samba.git synced 2025-11-27 08:23:49 +03:00
Commit Graph

13 Commits

Author SHA1 Message Date
Rafal Szczesniak
cd89cf9919 r7588: Fix lacking space in the comment.
rafal
2007-10-10 13:18:12 -05:00
Rafal Szczesniak
f6ef7b882a r7490: Rename functions and prefices s/rpc_composite/libnet_rpc/
This makes more clear where the functions belong to. Also
the rule will be that lowercased function names are not
part of "official" libnet API (though it doesn't mean one
absolutely cannot use them).

rafal
2007-10-10 13:17:59 -05:00
Rafal Szczesniak
a784c46dd4 r6718: Formatting fixes.
rafal
2007-10-10 13:16:37 -05:00
Rafal Szczesniak
08a8878436 r6624: I have put monitor function pointer into userinfo call, but I haven't put
any possibility to pass such pointer from calling function... :)

rafal
2007-10-10 13:16:32 -05:00
Rafal Szczesniak
227c9fb45b r6616: First (and totally untested) approach to monitoring userinfo
composite call.

rafal
2007-10-10 13:16:31 -05:00
Rafal Szczesniak
ebf151ca6e r6384: Formatting fixes.
rafal
2007-10-10 13:11:35 -05:00
Andrew Tridgell
01ea1e7762 r6165: fixed up the userinfo composite code. Fixes include:
- talloc should always be done in the right context. For example, when creating
  the userinfo_state structure, place it inside the composite
  structure, not directly on the pipe. If this isn't done then
  correct cleanup can't happen on errors (as cleanup destroys the top
  level composite context only)

- define private structures like userinfo_state in the userinfo.c
  code, not in the public header

- only keep the parameters we need in the state structure. For
  example, the domain_handle is only needed in the first call, so we
  don't need to keep it around in the state structure, but the level is
  needed in later calls, so we need to keep it

- always initialise [out,ref] parameters in RPC calls. The [ref] part
  means that the call assumes the pointer it has been given is
  valid. If you don't initialise it then you will get a segv on
  recv. This is why the code was dying.

- don't use internal strucrure elements like the pipe
  pipe->conn->pending outside of the internal rpc implementation. That
  is an internal list, trying to use it from external code will cause crashes.

- rpc calls assume that rpc call strucrures remain valid for the
  duration of the call. This means you need to keep the structures
  (such as "struct samr_Close") in the userinfo_state strucrure,
  otherwise it will go out of scope during the async processing

- need to remember to change c->state to SMBCLI_REQUEST_DONE when the
  request has finished in the close handler, otherwise it will loop
  forever trying to close

Mimir, please look at the diff carefully for more detailed info on the fixes
2007-10-10 13:11:23 -05:00
Rafal Szczesniak
01cbed98b3 r6164: More comments in the code.
rafal
2007-10-10 13:11:22 -05:00
Jelmer Vernooij
e193555f0e r5775: Remove some unused functions (unions are no longer as special as they used to be)
Add oxid mapping table support in DCOM
2007-10-10 13:11:02 -05:00
Rafal Szczesniak
ec177c9226 r5677: Split structure definitions from implementation.
rafal
2007-10-10 13:10:59 -05:00
Rafal Szczesniak
e5daf6911b r5576: Bunch of fixes pointed by tridge. A few more to come...
rafal
2007-10-10 13:10:54 -05:00
Rafal Szczesniak
bfb4dfaa8c r5474: Remove random notes put in code.
rafal
2007-10-10 13:10:48 -05:00
Rafal Szczesniak
dcab843da3 r5472: First approach to composite rpc call fetchin user info.
It does only compile. Completely untested yet, so almost certainly
broken, but I don't want it to lay on my laptop only.

rafal
2007-10-10 13:10:48 -05:00