Adds mutex-leak-move-deadlock for panic situation

Author: ruihe774

src/tools/miri/tests/fail/concurrency/mutex-leak-move-deadlock.rs

@@ -1,4 +1,5 @@
 //@error-in-other-file: deadlock
+//@ignore-target: linux
 //@normalize-stderr-test: "src/sys/.*\.rs" -> "$$FILE"
 //@normalize-stderr-test: "LL \| .*" -> "LL | $$CODE"
 //@normalize-stderr-test: "\| +\^+" -> "| ^"

src/tools/miri/tests/panic/mutex-leak-move-deadlock.rs

@@ -0,0 +1,16 @@
+//@only-target: linux
+//@normalize-stderr-test: "src/sys/.*\.rs" -> "$$FILE"
+//@normalize-stderr-test: "LL \| .*" -> "LL | $$CODE"
+//@normalize-stderr-test: "\| +\^+" -> "| ^"
+//@normalize-stderr-test: "\n *= note:.*" -> ""
+use std::mem;
+use std::sync::Mutex;
+
+fn main() {
+    let m = Mutex::new(0);
+    mem::forget(m.lock());
+    // Move the lock while it is "held" (really: leaked)
+    let m2 = m;
+    // Now try to acquire the lock again.
+    let _guard = m2.lock();
+}

src/tools/miri/tests/panic/mutex-leak-move-deadlock.stderr

@@ -0,0 +1,4 @@
+thread 'main' panicked at RUSTLIB/std/$FILE:LL:CC:
+failed to lock mutex: Os { code: 35, kind: Deadlock, message: "deadlock" }
+note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
+note: in Miri, you may have to set `MIRIFLAGS=-Zmiri-env-forward=RUST_BACKTRACE` for the environment variable to have an effect