From: Matthew Wilcox <willy@infradead.org>
To: Wander Lairson Costa <wander@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Brian Cain <bcain@quicinc.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Stafford Horne <shorne@gmail.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrei Vagin <avagin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
Yu Zhao <yuzhao@google.com>, Alexey Gladkov <legion@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Yang Shi <shy828301@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
Hu Chunyu <chuhu@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Luis Goncalves <lgoncalv@redhat.com>
Subject: Re: [PATCH v9] kernel/fork: beware of __put_task_struct calling context
Date: Tue, 16 May 2023 20:24:04 +0100 [thread overview]
Message-ID: <ZGPYVAF6Nkp2umaa@casper.infradead.org> (raw)
In-Reply-To: <20230516191441.34377-1-wander@redhat.com>
On Tue, May 16, 2023 at 04:14:41PM -0300, Wander Lairson Costa wrote:
> +void __put_task_struct_rcu_cb(struct rcu_head *rhp)
> +{
> + struct task_struct *task = container_of(rhp, struct task_struct, rcu);
> +
> + __put_task_struct(task);
> +}
> +EXPORT_SYMBOL_GPL(__put_task_struct_rcu_cb);
Why does this need to be exported when its only caller is within the
main kernel and cannot possibly be built as a module?
next prev parent reply other threads:[~2023-05-16 19:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 19:14 [PATCH v9] kernel/fork: beware of __put_task_struct calling context Wander Lairson Costa
2023-05-16 19:24 ` Matthew Wilcox [this message]
2023-05-16 21:05 ` Andrew Morton
2023-05-16 21:41 ` Matthew Wilcox
2023-05-16 22:50 ` Andrew Morton
2023-05-17 15:26 ` Oleg Nesterov
2023-05-17 16:57 ` Wander Lairson Costa
2023-05-29 12:22 ` Oleg Nesterov
2023-06-01 17:45 ` Wander Lairson Costa
2023-06-01 18:13 ` Oleg Nesterov
2023-06-01 18:23 ` Wander Lairson Costa
2023-06-02 17:34 ` Oleg Nesterov
2023-06-05 11:24 ` Wander Lairson Costa
2023-06-06 20:39 ` Oleg Nesterov
2023-06-09 19:07 ` Wander Lairson Costa
2023-06-02 17:39 ` Oleg Nesterov
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=ZGPYVAF6Nkp2umaa@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=bcain@quicinc.com \
--cc=bigeasy@linutronix.de \
--cc=bristot@kernel.org \
--cc=chuhu@redhat.com \
--cc=ebiederm@xmission.com \
--cc=legion@kernel.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=shorne@gmail.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=vschneid@redhat.com \
--cc=wander@redhat.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yuzhao@google.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