David Tolnay 1d4d44a8e2 sync: Mutex type with methods that panic instead of return error ... This CL adds a crate `sync` containing a type sync::Mutex which wraps the standard library Mutex and mirrors the same methods, except that they panic where the standard library would return a PoisonError. This API codifies our error handling strategy around poisoned mutexes in crosvm. - Crosvm releases are built with panic=abort so poisoning never occurs. A panic while a mutex is held (or ever) takes down the entire process. Thus we would like for code not to have to consider the possibility of poison. - We could ask developers to always write `.lock().unwrap()` on a standard library mutex. However, we would like to stigmatize the use of unwrap. It is confusing to permit unwrap but only on mutex lock results. During code review it may not always be obvious whether a particular unwrap is unwrapping a mutex lock result or a different error that should be handled in a more principled way. Developers should feel free to use sync::Mutex anywhere in crosvm that they would otherwise be using std::sync::Mutex. TEST=boot linux Change-Id: I9727b6f8fee439edb4a8d52cf19d59acf04d990f Reviewed-on: https://chromium-review.googlesource.com/1359923 Commit-Ready: David Tolnay <dtolnay@chromium.org> Tested-by: David Tolnay <dtolnay@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>		2018-12-05 01:13:41 -08:00
..
src	sync: Mutex type with methods that panic instead of return error	2018-12-05 01:13:41 -08:00
build.rs	cargo fmt all source code	2018-10-09 21:14:05 -07:00
Cargo.toml	sync: Mutex type with methods that panic instead of return error	2018-12-05 01:13:41 -08:00
host_cpuid.c	x86_64: fill cache info in cpuid, stop spoofing CPU vendor id	2018-07-09 12:42:42 -07:00