From 83298a7b5d5ed591986a1eb5f633bce38dae40be Mon Sep 17 00:00:00 2001
From: Jimi Chen <jimictw@google.com>
Date: Fri, 18 Jul 2025 06:11:15 +0000
Subject: [PATCH] Use Log.e for procfs file read errors

Log.wtf implies a catastrophic, unrecoverable failure. Failures to read
procfs files (e.g., due to permissions or non-existence) are better
represented by Log.e as they are often recoverable or expected under
certain conditions, and not always indicative of a fatal application state.

Flag: EXEMPT mainline
Bug: 429012888
Test: TH
Change-Id: I717d46d4c3802ac478e80d2a9dd28c79a9ebc5f7
---
 .../device/com/android/net/module/util/ProcfsParsingUtils.java  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/staticlibs/device/com/android/net/module/util/ProcfsParsingUtils.java b/staticlibs/device/com/android/net/module/util/ProcfsParsingUtils.java
index 3bd1e6c123..07a98c312f 100644
--- a/staticlibs/device/com/android/net/module/util/ProcfsParsingUtils.java
+++ b/staticlibs/device/com/android/net/module/util/ProcfsParsingUtils.java
@@ -78,7 +78,7 @@ public final class ProcfsParsingUtils {
                 lines.add(line);
             }
         } catch (IOException e) {
-            Log.wtf(TAG, "failed to read " + filePath, e);
+            Log.e(TAG, "failed to read " + filePath, e);
         }
 
         return lines;