tracing: Dump stacktrace trigger to the corresponding instance

mainline inclusion
from mainline-v5.17-rc6
commit ce33c845
category: bugfix
bugzilla: https://gitee.com/openeuler/kernel/issues/I5ISAH
CVE: NA

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ce33c845b030c9cf768370c951bc699470b09fa7

--------------------------------

The stacktrace event trigger is not dumping the stacktrace to the instance
where it was enabled, but to the global "instance."

Use the private_data, pointing to the trigger file, to figure out the
corresponding trace instance, and use it in the trigger action, like
snapshot_trigger does.

Link: https://lkml.kernel.org/r/afbb0b4f18ba92c276865bc97204d438473f4ebc.1645396236.git.bristot@kernel.org



Cc: stable@vger.kernel.org
Fixes: ae63b31e ("tracing: Separate out trace events from global variables")
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
Tested-by: Tom Zanussi <zanussi@kernel.org>
Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

[zzk: __trace_stack() was changed due to the merge of "36590c50 tracing: Merge irqflags + preempt counter",
cherry-pick from mainline ce33c845 instead of stable 5.10.y]

Signed-off-by: Zheng Zengkai <zhengzengkai@huawei.com>
Reviewed-by: Yang Jihong <yangjihong1@huawei.com>
Acked-by: Xie XiuQi <xiexiuqi@huawei.com>