summaryrefslogtreecommitdiff
path: root/source3/include
diff options
context:
space:
mode:
authorChristopher R. Hertel <crh@samba.org>1998-04-13 22:45:52 +0000
committerChristopher R. Hertel <crh@samba.org>1998-04-13 22:45:52 +0000
commitd5e040247e180664bd32a0d7d8dd905f46cbdb47 (patch)
tree1e30e2ba34eb5b25d7bc2d5214db0f54ede07bad /source3/include
parentcac6a060af598bf94e6414b06e7365ec51ca360e (diff)
downloadsamba-d5e040247e180664bd32a0d7d8dd905f46cbdb47.tar.gz
samba-d5e040247e180664bd32a0d7d8dd905f46cbdb47.tar.bz2
samba-d5e040247e180664bd32a0d7d8dd905f46cbdb47.zip
Changes include:
proto.h: The unusual. ;) reply.c: I changes some function names, and updated reply.c to match. See mangle.c below for more. server.c: Changed function names and parameters in file mangle.c, so changed server.c calls to match. See mangle.c below for more. mangle.c: I replaced the caching mechanism used for caching reverse mangled name maps. The old method was a large array of 256-byte strings. Movement in the stack (including push and pop) was done by memcpy()ing whole chunks of memory around. The new system uses the ubi_Cache module which, in turn, uses a splay tree. Entries are dynamically allocated using a minimum amount of memory. Searches are non-linear, which should speed things up a bit, too. Overall, this should save memory and be faster. Other changes: I streamlined the is_mangled() test and made other speed enhancements including replacing some static functions with macros. Added comments, etc. Note: Per an E'mail conversation with Andrew, the 'mangled stack' parameter in smb.conf doesn't do anything anymore. The cache is now set for 16K bytes maximum memory usage. The mangle stack parameter is silently ignored. This can easily be changed, but I'd rather introduce a 'mangled cache memory' parameter and remove 'mangled stack'. Remaining problems: While testing the module, I noticed that something is calling name_map_mangle() twice. The result is that names which contain illegal characters are getting mangled twice. Also, the entire module works by overwriting the input string. This has a variety of nasty side effects. Summary: There's a lot still to be done, but the changes I have in place *should* work in exactly the same way (except for the mangle stack parameter). The rest of the bugs and other issues are separate. Chris -)----- (This used to be commit 8759bec11ba483b2292b0e513b85c98ed5e3e2d4)
Diffstat (limited to 'source3/include')
-rw-r--r--source3/include/proto.h12
1 files changed, 6 insertions, 6 deletions
diff --git a/source3/include/proto.h b/source3/include/proto.h
index fb95a7d525..3e1f9f5fa3 100644
--- a/source3/include/proto.h
+++ b/source3/include/proto.h
@@ -1078,13 +1078,13 @@ struct share_ops *locking_slow_init(int ronly);
/*The following definitions come from mangle.c */
-int str_checksum(char *s);
-BOOL is_8_3(char *fname, BOOL check_case);
-void reset_mangled_stack( int size );
-BOOL check_mangled_stack(char *s);
BOOL is_mangled( char *s );
-void mangle_name_83(char *s);
-BOOL name_map_mangle(char *OutName,BOOL need83,int snum);
+BOOL is_8_3( char *fname, BOOL check_case );
+int str_checksum( char *s );
+void reset_mangled_cache( void );
+BOOL check_mangled_cache( char *s );
+void mangle_name_83( char *s );
+BOOL name_map_mangle( char *OutName, BOOL need83, int snum );
/*The following definitions come from md4.c */