From: Daniel Walker <dwalker@mvista.com>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: try_module_get and friends
Date: Wed, 05 Mar 2008 11:30:55 -0800 [thread overview]
Message-ID: <1204745455.17630.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1204661228.8244.15.camel@jcmlaptop>
On Tue, 2008-03-04 at 15:07 -0500, Jon Masters wrote:
> On Tue, 2008-03-04 at 00:28 -0500, Jon Masters wrote:
> > On Tue, 2008-03-04 at 00:20 -0500, Jon Masters wrote:
> >
> > > So, what's protecting the RT kernel from falling over if a CPU frequency
> > > governor module is removed at the wrong moment?
> >
> > That's a contrived example, it does the right thing in the ones I've
> > looked it, but it just occurred to me that this might not be general for
> > kernel code where random pointers to modules are getting thrown around.
>
> I recommend not setting CONFIG_MODULE_UNLOAD on RT kernels for now. I
> looked at programmatically implementing this in Kconfig, but it seems
> that CONFIG_MODULE_UNLOAD is never explicitly set anywhere, it's simply
> in the deconfig for each architecture - anyone know Kconfig well enough
> to tell us how to fix up Kconfig.preempt to do the right thing?
Could you give a different of better example of the problem with
modules? This thread has been fairly scant on details ..
Daniel
next prev parent reply other threads:[~2008-03-05 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 5:20 try_module_get and friends Jon Masters
2008-03-04 5:28 ` Jon Masters
2008-03-04 20:07 ` Jon Masters
2008-03-05 19:30 ` Daniel Walker [this message]
2008-03-05 19:47 ` Steven Rostedt
2008-03-05 20:28 ` Daniel Walker
2008-03-05 20:46 ` Frank Ch. Eigler
2008-03-05 20:54 ` Steven Rostedt
2008-03-05 21:15 ` Daniel Walker
2008-03-07 16:16 ` Paul E. McKenney
2008-03-05 21:14 ` Steven Rostedt
2008-03-10 5:53 ` Jon Masters
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=1204745455.17630.8.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=jonathan@jonmasters.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.