loom: loom::std::parking_lot::RwLock try_read/try_write methods block

bd4ccae introduced a wrapper for the
RwLock to get rid of poisoning aspects.

By mistake (?!) its try_read/write methods actually delegate to
read/write() and this would lead to blocking

Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>

Author: martin-g

tokio/src/loom/std/parking_lot.rs

@@ -6,7 +6,7 @@
 use std::fmt;
 use std::marker::PhantomData;
 use std::ops::{Deref, DerefMut};
-use std::sync::LockResult;
+use std::sync::{LockResult, TryLockError};
 use std::time::Duration;
 
 // All types in this file are marked with PhantomData to ensure that
@@ -101,15 +101,21 @@ impl<T> RwLock<T> {
     }
 
     pub(crate) fn try_read(&self) -> Option<RwLockReadGuard<'_, T>> {
-        Some(RwLockReadGuard(PhantomData, self.1.read()))
+        match self.1.try_read() {
+            Some(guard) => Some(RwLockReadGuard(PhantomData, guard)),
+            None => None,
+        }
     }
 
     pub(crate) fn write(&self) -> RwLockWriteGuard<'_, T> {
         RwLockWriteGuard(PhantomData, self.1.write())
     }
 
     pub(crate) fn try_write(&self) -> Option<RwLockWriteGuard<'_, T>> {
-        Some(RwLockWriteGuard(PhantomData, self.1.write()))
+        match self.1.try_write() {
+            Some(guard) => Some(RwLockWriteGuard(PhantomData, guard)),
+            None => None,
+        }
     }
 }