On Fri, May 18, 2007 at 04:01:21PM -0700, Luck, Tony wrote: > If the problem *only* occurs when trying to get_wchan on the > current task (a futile endevour) then the original patch > should be fine all by itself ... there are no races involved > the current task is going to remain in TASK_RUNNING state at > any point that it happens to look at itself. The problem I was seeing was only on the current task, but we could have two seperate threads creating that situation. I could certain see the argument for adding the sanity checks to the current unwind code or verifying that libunwind does not suffer the same race conditions. I will leave it to your discretion. Thanks, Robin - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|