asterisk.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2016-02-25	res_sorcery_memory_cache: Fix SEGV in some CLI commands	George Joseph
	A few of the CLI commands weren't checking for enough arguments and were SEGVing. Change-Id: Ie6494132ad2fe54b4f014bcdc112a37c36a9b413
2015-12-17	res_sorcery_memory_cache: Add support for a full backend cache.	Joshua Colp
	This change introduces the configuration option 'full_backend_cache' which changes the cache to be a full mirror of the backend instead of a per-object cache. This allows all sorcery retrieval operations to be carried out against it and is useful for object types which are used in a "retrieve all" or "retrieve some" pattern. ASTERISK-25625 #close Change-Id: Ie2993487e9c19de563413ad5561c7403b48caab5
2015-12-01	res_sorcery_memory_cache.c: Fix off nominal ref leak.	Richard Mudgett
	Change-Id: If83d63cf11cbc6df9b15251848b01feb570ade49
2015-10-01	res_sorcery_memory_cache.c: Fix deadlock with scheduler.	Richard Mudgett
	A deadlock can happen when a sorcery object is being expired from the memory cache when at the same time another object is being placed into the memory cache. There are a couple other variations on this theme that could cause the deadlock. Basically if an object is being expired from the sorcery memory cache at the same time as another thread tries to update the next object expiration timer the deadlock can happen. * Add a deadlock avoidance loop in expire_objects_from_cache() to check if someone is trying to remove the scheduler callback from the scheduler. ASTERISK-25441 #close Change-Id: Iec7b0bdb81a72b39477727b1535b2539ad0cf4dc
2015-10-01	res_sorcery_memory_cache.c: Replace inline code with function.	Richard Mudgett
	Make sorcery_memory_cache_close() call remove_all_from_cache() instead of partially inlining it. ASTERISK-25441 Change-Id: I1aa6cb425b1a4307096f3f914d17af8ec179a74c
2015-10-01	res_sorcery_memory_cache.c: Shutdown in a less crash potential order.	Richard Mudgett
	Basically you should shutdown in the opposite order of how you setup since later setup pieces likely depend on earlier setup pieces. e.g., Registering your external API with the rest of the system should be the last thing setup and the first thing unregistered during shutdown. Change-Id: I5715765b723100c8d3c2642e9e72cc7ad5ad115e
2015-10-01	res_sorcery_memory_cache.c: Misc tweaks.	Richard Mudgett
	Change-Id: I8cd32dffbb4f33bb0c39518d6e4c991e73573160
2015-10-01	res_sorcery_memory_cache.c: Made use OBJ_SEARCH_MASK.	Richard Mudgett
	Change-Id: Ibca6574dc3c213b29cc93486e01ccd51f5caa46c
2015-07-10	res/res_sorcery_memory_cache: Fix test registration issues	Matt Jordan
	Again, tests now need to not end with a newline. This patch makes it so the tests can register again, unit tests will actually pass, and we can stop wasting time trying to figure out why builds are failing when they really aren't failing. Change-Id: Ide519fbeba89f413c733446c5ff7b224fc4ce840
2015-07-09	res_sorcery_memory_cache: Backport to 13	Joshua Colp
	Gerrit is complaining of conflicts when trying to create a patch series of all of the cherry-picked master commits, so I have instead squashed it all into one commit. ASTERISK-25067 #close Reported by: Matt Jordan Change-Id: I6dda90343fae24a75dc5beec84980024e8d61eb9