CVS update: samba/source/rpc_pipes

Luke Leighton lkcl at samba.anu.edu.au
Sun Dec 14 07:14:51 EST 1997


Date:	Sunday December 14, 1997 @ 7:14
Author:	lkcl

Update of /data/cvs/samba/source/rpc_pipes
In directory samba:/tmp/cvs-serv24548/rpc_pipes

Modified Files:
      Tag: BRANCH_NTDOM
	lsaparse.c netparse.c pipe_hnd.c pipenetlog.c pipentlsa.c 
	pipereg.c pipesamr.c pipesrvsvc.c pipeutil.c pipewkssvc.c 
	regparse.c samrparse.c smbparse.c srvparse.c wksparse.c 
Log Message:

Issues
------

client and server need to deal with DCE/RPC data larger than an SMB
response buffer.  this is handled at the server end by putting a
warning (0x80000000) of NT_STATUS_BUFFER_TOO_SMALL in the DCE/RPC
response, keeping a copy of the data and then waiting for a SMBreadX.

the buffer parsing (for both client and server) has had to be updated
to cope with dynamic reallocation of the buffers (> 1024 bytes).

the server-side has been rewritten: the client-side has _not_.  i will
do that tomorrow.  therefore, smbd compiles; nmbd compiles; smbclient
does not.  it will tomorrow.

pipe_hnd.c has a read_pipe command, and a write_pipe command.  these
are not hooked in, yet.

i have a bug-bear with the new struct mem_buffer: if you want to use
this structure, DO NOT use the data_ptr member: i will be removing it
at the earliest opportunity.


Modified Files
--------------

i am sorry, i am _not_ going to describe every detail of a change that
results in an 8,491 diff file.


Added Files
-----------

memparse.c :

	new memory allocation structure.  stores the actual size and the
	used size, and a safety margin.  call buf_grow with the new size,
	and it will allocate a bit on the end.  you can therefore
	"retrospectively" grow some dynamic memory, as long as your
	safety margin is big enough.

	maybe we want to ensure that the memory is realloced in multiples
	of safety margin, so as not to fragment memory too much.

	DON'T USE THE data_ptr MEMBER: I HATE IT!




More information about the samba-cvs mailing list