From: Peter Zijlstra <peterz@infradead.org>
To: Denis Efremov <efremov@linux.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jason Baron <jbaron@akamai.com>
Subject: Re: Unloading a module with a function which is used by a static call
Date: Fri, 17 Sep 2021 22:10:01 +0200 [thread overview]
Message-ID: <20210917201001.GJ4323@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <d72f55fc-bbe2-b02d-0a90-ad6aaef8810e@linux.com>
On Fri, Sep 17, 2021 at 11:07:22PM +0300, Denis Efremov wrote:
> Hi,
>
> I'm not sure, but is it intentional that we don't increase a module refcounter
> when we call static_call_update()? Let's imagine that:
For all intents and purposes, static_call_update() is the same as
assinging a function pointer. That also doesn't increment module counts.
If your case requires management of module refcounts, you get to do so.
prev parent reply other threads:[~2021-09-17 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 20:07 Unloading a module with a function which is used by a static call Denis Efremov
2021-09-17 20:10 ` Peter Zijlstra [this message]
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=20210917201001.GJ4323@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=efremov@linux.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.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