All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: dwalker@mvista.com
Cc: ganzinger@mvista.com, Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: del_timer_sync needed for UP  RT systems.
Date: Tue, 26 Apr 2005 17:34:33 -0700	[thread overview]
Message-ID: <426EDE19.3030600@mvista.com> (raw)
In-Reply-To: <1114561446.12772.71.camel@dhcp153.mvista.com>

Daniel Walker wrote:
> On Tue, 2005-04-26 at 17:14, George Anzinger wrote:
> 
> 
>>The problem here is that the reference is to timr, a pointer to something which 
>>has been deleted.  The memory may well be used elsewhere by this time which will 
>>make the test of it_process wrong.  It also means we could mess with someone 
>>elses memory in the memset above.
> 
> 
> Bottom line, you can use sys_timer_delete() on a timer, and trigger the
> same timer your deleting .. Those operations should be serialized, which
> they currently aren't .. 

I agree.  The change to do this is to use the del_timer_sync() or the 
del_singleshot_timer() code.

It is possible and desirable to be able to delete a running timer.  We don't 
want to take it away from the timer call back routine, however, as that leads to 
"bad things".  That is why these two del_* routines were written.
> 
-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/

  parent reply	other threads:[~2005-04-27  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 23:42 del_timer_sync needed for UP RT systems George Anzinger
2005-04-26 23:55 ` Daniel Walker
2005-04-27  0:14   ` George Anzinger
2005-04-27  0:24     ` Daniel Walker
2005-04-27  0:30       ` Daniel Walker
2005-04-27  0:34       ` George Anzinger [this message]
2005-04-27  0:50         ` Daniel Walker

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=426EDE19.3030600@mvista.com \
    --to=george@mvista.com \
    --cc=dwalker@mvista.com \
    --cc=ganzinger@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.