From: Petr Pavlu <petr.pavlu@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH 5/8] module: Add module_for_each_mod() function
Date: Mon, 10 Feb 2025 14:04:35 +0100 [thread overview]
Message-ID: <bfe05b54-9714-46bc-9b59-ad091897c62d@suse.com> (raw)
In-Reply-To: <20250206102720.0fd57129@gandalf.local.home>
On 2/6/25 16:27, Steven Rostedt wrote:
> On Thu, 6 Feb 2025 14:28:17 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
>>> --- a/kernel/module/main.c
>>> +++ b/kernel/module/main.c
>>> @@ -3809,6 +3809,20 @@ bool is_module_text_address(unsigned long addr)
>>> return ret;
>>> }
>>>
>>
>> It is better to add a kerneldoc for this API.
>
> Agreed, but I was planning on this changing. Waiting to hear from the
> module maintainers.
>
>>
>> /**
>> * module_for_each_mod() - iterate all modules
>> * @func: Callback function
>> * @data: User data
>> *
>> * Call the @func with each module in the system. If @func returns !0, this
>> * stops itrating. Note that @func must not sleep since it is called under
>> * the preemption disabled.
>> */
>>
>> BTW, do we really need to disable preempt or is it enough to call
>> rcu_read_lock()?
>
> Bah, as I expected this function to be changed, I didn't spend too much
> time on looking at its implementation. I just cut and pasted how the other
> loops worked. But yes, it should not be disabling preemption. In fact, I
> think the module code itself should not be disabling preemption!
>
> I'll have to go and look into that.
The series "module: Use RCU instead of RCU-sched" from Sebastian Andrzej
Siewior cleans this up [1]. It is currently queued on modules-next (for
6.15-rc1).
The new function module_for_each_mod() should then use "guard(rcu)();".
[1] https://lore.kernel.org/linux-modules/20250108090457.512198-1-bigeasy@linutronix.de/
--
Thanks,
Petr
>>> +void module_for_each_mod(int(*func)(struct module *mod, void *data), void *data)
>>> +{
>>> + struct module *mod;
>>> +
>>> + preempt_disable();
>>> + list_for_each_entry_rcu(mod, &modules, list) {
>>> + if (mod->state == MODULE_STATE_UNFORMED)
>>> + continue;
>>> + if (func(mod, data))
>>> + break;
>>> + }
>>> + preempt_enable();
>>> +}
>>> +
>>> /**
>>> * __module_text_address() - get the module whose code contains an address.
>>> * @addr: the address.
>>> --
>
next prev parent reply other threads:[~2025-02-10 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250205225031.799739376@goodmis.org>
2025-02-05 22:50 ` [PATCH 5/8] module: Add module_for_each_mod() function Steven Rostedt
2025-02-06 5:28 ` Masami Hiramatsu
2025-02-06 15:27 ` Steven Rostedt
2025-02-10 13:04 ` Petr Pavlu [this message]
2025-02-10 14:08 ` Sebastian Andrzej Siewior
2025-02-14 22:30 ` Steven Rostedt
2025-02-18 21:21 ` Luis Chamberlain
2025-02-18 21:29 ` Steven Rostedt
2025-02-19 0:24 ` Steven Rostedt
2025-02-19 16:02 ` Luis Chamberlain
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=bfe05b54-9714-46bc-9b59-ad091897c62d@suse.com \
--to=petr.pavlu@suse.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@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