On 7/30/25 6:32 AM, Steven Rostedt wrote:
On Tue, 29 Jul 2025 21:55:39 -0700
Indu Bhagat <indu.bhagat@xxxxxxxxxx> wrote:
diff --git a/include/linux/unwind_deferred.h b/include/linux/unwind_deferred.h
index a5f6e8f8a1a2..baacf4a1eb4c 100644
--- a/include/linux/unwind_deferred.h
+++ b/include/linux/unwind_deferred.h
@@ -12,6 +12,12 @@ void unwind_task_free(struct task_struct *task);
int unwind_user_faultable(struct unwind_stacktrace *trace);
+static __always_inline void unwind_reset_info(void)
+{
+ if (unlikely(current->unwind_info.cache))
+ current->unwind_info.cache->nr_entries = 0;
+}
Should the entries[] items upto nr_entries (stack trace info from the
previous request) also be reset to 0 here ?
This is in a critical path, there's no reason to reset to zero. The data will
just be stale. Nothing should care about anything over nr_entries.
OK.
Reviewed-By: Indu Bhagat <indu.bhagat@xxxxxxxxxx>
