All of lore.kernel.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Walker <dwalker@mvista.com>,
	Jon Masters <jonathan@jonmasters.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 15:46:59 -0500	[thread overview]
Message-ID: <y0mr6eo99vg.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0803051442330.15217@gandalf.stny.rr.com> (Steven Rostedt's message of "Wed, 5 Mar 2008 14:47:28 -0500 (EST)")


Steven Rostedt <rostedt@goodmis.org> writes:

> [...]
> There's a theoretical potential for the system to crash in -rt when
> unloading a module. Simply because interrupts are threads.
>
> Some device has an interrupt handler that is called and preempted.
> At that moment the module for that device is unloaded. [...]
> Since the code for the interrupt handler no longer exists... KABOOM!

Perhaps you can identify those modules that have asked for interrupts,
and block only them from unloading.  Or, would it be outrageously
expensive to increment the module refcount while one of its interrupt
handlers is running?

- FChE

  parent reply	other threads:[~2008-03-05 20:52 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
2008-03-05 19:47       ` Steven Rostedt
2008-03-05 20:28         ` Daniel Walker
2008-03-05 20:46         ` Frank Ch. Eigler [this message]
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=y0mr6eo99vg.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=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.