From 41c4bea27c7dca0223a418296182f46a82e5a050 Mon Sep 17 00:00:00 2001
From: Christopher Tate <ctate@android.com>
Date: Fri, 4 Dec 2009 11:05:12 -0800
Subject: [PATCH] Don't accidentally signal multiple exceptions in
 setThreadPriority()

After signalling an exception due to set_sched_policy() failing (probably
because the thread in question had exited before this function was called), we
proceeded to call setpriority() anyway, and raised *another* exception when it
also failed.  We don't do this any more; we just bail after signalling the first
exception.

Change-Id: I397b6a93c73d3f0870176e26759f2bec33e56205
---
 core/jni/android_util_Process.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/core/jni/android_util_Process.cpp b/core/jni/android_util_Process.cpp
index f1c1cb966a510..094b02d140941 100644
--- a/core/jni/android_util_Process.cpp
+++ b/core/jni/android_util_Process.cpp
@@ -285,6 +285,7 @@ void android_os_Process_setThreadPriority(JNIEnv* env, jobject clazz,
 
     if (rc) {
         signalExceptionForGroupError(env, clazz, errno);
+        return;
     }
 
     if (setpriority(PRIO_PROCESS, pid, pri) < 0) {