Andrew Bartlett e68684aa65 Fix 2 off-by-one bugs in the use of malloc()ed strings and safe_strcpy(). ...

safe_strcpy() isn't particularly safe (this has been noted before) as it does
not take the size of the buffer, but instead the size of the buffer *minus 1*

The locking.c fix was causing segfaults on machines running with
--enable-developer, and was tracked down thanks to the fact that vance's build
farm machine runs with such an option, and smbtorture's DIR1 test hits this
bug very well.

(The --enable-developer code writes to the last byte of the string, to check
for incorrect use of safe_strcpy()).

Andrew Bartlett
(This used to be commit e908fd164d1b11b6f76a6fdffb22e139813cb3c0)

2003-02-24 01:13:31 +00:00

..

brlock.c

When checking is_locked() new WRITE locks conflict with existing READ locks even

2003-02-22 01:09:42 +00:00

locking.c

Fix 2 off-by-one bugs in the use of malloc()ed strings and safe_strcpy().

2003-02-24 01:13:31 +00:00

posix.c

Fixes for HPUX only having limited POSIX lock range from Michael Steffens <michael.steffens@hp.com>

2003-02-12 20:38:02 +00:00