summaryrefslogtreecommitdiff
path: root/source3/smbd/reply.c
diff options
context:
space:
mode:
authorChristopher R. Hertel <crh@samba.org>1997-11-07 03:06:24 +0000
committerChristopher R. Hertel <crh@samba.org>1997-11-07 03:06:24 +0000
commitf9bbcb3fb3effdeb9f9f42de77bbde9f2789efdc (patch)
tree755bdaec84808f6d7f463ba4c53fc5b3badfa289 /source3/smbd/reply.c
parent36e5b646d9d6f40b44a9c851c5f8caa499eb2237 (diff)
downloadsamba-f9bbcb3fb3effdeb9f9f42de77bbde9f2789efdc.tar.gz
samba-f9bbcb3fb3effdeb9f9f42de77bbde9f2789efdc.tar.bz2
samba-f9bbcb3fb3effdeb9f9f42de77bbde9f2789efdc.zip
Modified Files:
mangle.c server.c proto.h mangle.c I am planning to replace the mangled_stack array with a proper stack, but found many style inconsistencies (no, really). As you might expect, I have standardized on my own preferences. ;) I also found a potential problem in create_mangled_stack (which I've renamed as reset_mangled_stack). If the stack size were passed into the function as 0 or less, there was the possibility that the array would have been freed twice. I doubt that this ever happens, but I don't like to leave holes. Of course, the fix will be irrelevent once I replace the array with a linked-list-based stack. server.c Changed the call to create_mangled_stack() to a call to reset_mangled_stack(). proto.h Regenerated to match the above changes. (A real comment! How unusual!) (This used to be commit 34d1b3e4fa7a1158f3a3c5c47adf0417c7144095)
Diffstat (limited to 'source3/smbd/reply.c')
0 files changed, 0 insertions, 0 deletions