[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250218162942.5267a002@gandalf.local.home>
Date: Tue, 18 Feb 2025 16:29:42 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Mark
Rutland <mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Petr Pavlu <petr.pavlu@...e.com>, Sami
Tolvanen <samitolvanen@...gle.com>, Daniel Gomez <da.gomez@...sung.com>,
linux-modules@...r.kernel.org
Subject: Re: [PATCH 5/8] module: Add module_for_each_mod() function
On Tue, 18 Feb 2025 13:21:20 -0800
Luis Chamberlain <mcgrof@...nel.org> wrote:
> > Luis,
> >
> > Is this patch OK, and also is there any plan to move the module code to
> > using just rcu_read_lock instead of preempt_disable?
>
> The patch is not OK, you're looking at old code, look at
> modules-next and as Petr suggested look at Sebastian's recently
> merged work.
>
> git remote add korg-modules git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git
Ha! Some how I missed seeing the two replies from Petr and Sebastian!
Not sure how that happened. Something may be going wacky with claws-mail. :-/
Thanks for pointing them out. I'll definitely take a look.
-- Steve
Powered by blists - more mailing lists