Travis Cross 622e0e1a6f Check for null hash on increment of mod_hash limit ... When we specifically release all limits on a channel we destroy the hash table stored in the "limit_hash" private channel data but we don't destroy the private data as it will be reclaimed as part of the session. If limit increment is called after the limit release we can reuse that channel private, but we need to check whether the hash table is null first. Fortunately this makes the code look better anyway. FS-6775 #resolve FS-6783 #resolve		2014-09-11 17:47:57 +00:00
..
conf	conf: add config files to module directories	2012-03-24 04:51:08 +00:00
Makefile.am	FS-6293: srcdir builds, most of the built in mods work now	2014-03-14 23:13:34 -04:00
mod_hash.2008.vcproj	Fix Windows build	2010-07-19 12:47:09 -05:00
mod_hash.2010.vcxproj	Fix Windows build	2010-07-19 12:47:09 -05:00
mod_hash.2012.vcxproj	Disabled some compiler warnings on Windows build (for Visual Studio 2012), also disabled code analysis one some projects. This should make the Windows build more clean in the future.	2014-01-22 22:47:11 +01:00
mod_hash.c	Check for null hash on increment of mod_hash limit	2014-09-11 17:47:57 +00:00