From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Jiri Olsa <olsajiri@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Question on perf event context swap at process switch
Date: Fri, 22 Jul 2022 20:17:25 +0530 [thread overview]
Message-ID: <78aff052-64f1-a044-6ed3-e5f48325476f@amd.com> (raw)
Hi Peter,
Consider two processes having clone contexts (for example, two children of
the same parent). While process switch between these two, the perf event
context would get swapped but event->hw.target will point to other sibling's
task_struct. If that process exit just after one context swap, _free_event()
will call put_task_context() on sibling process' task_struct. Wouldn't it
result into fatal error later?
Thanks,
Ravi
reply other threads:[~2022-07-22 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78aff052-64f1-a044-6ed3-e5f48325476f@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®