RE: Timer manipulation in 2.6.13

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I did del_timer only before closing the device file and there was no OOPS.
Is it necessary to do del_timer(_sync) before closing the device/ unloading
the device?

~Abu

Abu M. Muttalib
Sr. Engineer, Embedded System,
Aftek Infosys Ltd.,
Pune, India
Office: 91-20-25449260-65 X-256
Mobile: (0)9881322820
Email: abum@xxxxxxxxx



-----Original Message-----
From: kernelnewbies-bounce@xxxxxxxxxxxx
[mailto:kernelnewbies-bounce@xxxxxxxxxxxx]On Behalf Of Arjan van de Ven
Sent: Saturday, February 25, 2006 9:23 PM
To: Abu M. Muttalib
Cc: kernelnewbies@xxxxxxxxxxxx
Subject: RE: Timer manipulation in 2.6.13


On Sun, 2006-02-26 at 08:59 +0530, Abu M. Muttalib wrote:
> Hi Arjan,
>
> Thanks again.
>
> I guess you defined the function modify_timer to return void and you have
run the driver only once.

I ran it several times, at least the echo you said

I did not unload and then reload the driver;
if you do that to get the oops then yes you need to do del_timer_sync()
before the unload!

(and you need the _sync version, not just the regular del_timer()
because you want to be really sure that the timer is finished before the
module goes away)


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux