Mark Salyzyn 7a2a307192 liblog: resolve deadlocks ... Although ever present, an increased regression introduced with commit b6bee33182 (liblog: logd: support logd.timestamp = monotonic). A signal handler can interrupt in locked context, if log is written in the signal handler, we are in deadlock. Block signals while we are locked. Separate out timestamp lock from is loggable lock to reduce contention situations. Provide a best-guess response if lock would fail in timestamp path. Bug: 25563384 Change-Id: I6dccd6b99ebace1c473c03a785a35c63ed5c6a8a		2015-11-12 15:39:04 -08:00
..
event_tag_map.h	Move liblog headers to system/core/include/log	2013-07-24 12:32:39 -07:00
log.h	liblog: resolve deadlocks	2015-11-12 15:39:04 -08:00
log_read.h	liblog: Add log_time += operator	2015-01-05 16:27:54 +00:00
logd.h	Kill HAVE_PTHREADS.	2015-01-27 14:23:22 -08:00
logger.h	liblog: add android_log_timestamp() private function	2015-10-29 14:23:42 -07:00
logprint.h	liblog: logcat: add epoch and monotonic format modifiers	2015-10-29 14:23:42 -07:00
uio.h	Only Windows doesn't have <sys/uio.h>.	2014-11-25 13:27:43 -08:00