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 [email protected]
High-res-timers: http://sourceforge.net/projects/high-res-timers/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
