From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Schspa Shi <schspa@gmail.com>,
linux-kernel@vger.kernel.org, cocci@inria.fr, mcgrof@kernel.org,
Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
buytenh@wantstofly.org, johannes.berg@intel.com,
gregkh@linuxfoundation.org, tomba@kernel.org, airlied@gmail.com,
daniel@ffwll.ch
Subject: Re: [RFC PATCH] cocci: cpi: add complete api check script
Date: Mon, 27 Feb 2023 16:43:59 +0100 [thread overview]
Message-ID: <Y/zPv+L2iqOkD2Oa@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230227102808.2cea9705@gandalf.local.home>
On Mon, Feb 27, 2023 at 10:28:08AM -0500, Steven Rostedt wrote:
> So what exact race are you trying to catch here?
on-stack copmletion with a wait_for_completion that can return early
(eg. killable, interruptible, or timeout) can go out of scope (eg, free
the completion) with the other side calling complete() on some possibly
re-used piece of stack.
IOW, Use-after-Free.
Care must be taken to ensure the other side (whatever does complete())
is either terminated or otherwise stopped from calling complete() on an
out-of-scope variable.
next prev parent reply other threads:[~2023-02-27 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 7:53 Schspa Shi
2023-02-27 11:20 ` Peter Zijlstra
2023-02-27 15:28 ` Steven Rostedt
2023-02-27 15:43 ` Peter Zijlstra [this message]
2023-02-27 15:53 ` Steven Rostedt
2023-02-27 16:36 ` Schspa Shi
2023-02-27 16:10 ` Schspa Shi
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=Y/zPv+L2iqOkD2Oa@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Julia.Lawall@inria.fr \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=buytenh@wantstofly.org \
--cc=cocci@inria.fr \
--cc=daniel@ffwll.ch \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mcgrof@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=nicolas.palix@imag.fr \
--cc=rostedt@goodmis.org \
--cc=schspa@gmail.com \
--cc=tomba@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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®