From: george anzinger <george@mvista.com>
To: Emmanuel Michon <emmanuel_michon@realmagic.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tasklet scheduled after end of rmmod
Date: Fri, 24 May 2002 10:11:33 -0700 [thread overview]
Message-ID: <3CEE7445.3B45DC44@mvista.com> (raw)
In-Reply-To: <7wptzlllek.fsf@avalon.france.sdesigns.com>
Emmanuel Michon wrote:
>
> Hi,
>
> as far as I understand nothing prevents a scheduled tasklet to have
> Linux jump to its routine, when the routine is in a module being
> rmmod'd. How should I take care of this?
>
> Are timers safe regarding this (I mean, we can consider the timer
> function won't be called as soon as del_timer() has returned)?
No, but del_timer_sync() is. See comments in
.../kernel/timer.c
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-05-24 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 13:34 tasklet scheduled after end of rmmod Emmanuel Michon
2002-05-24 17:11 ` george anzinger [this message]
2002-05-27 10:15 ` Ingo Oeser
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=3CEE7445.3B45DC44@mvista.com \
--to=george@mvista.com \
--cc=emmanuel_michon@realmagic.fr \
--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