From: Bill Davidsen <davidsen@tmr.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org,
Chuck Ebbert <76306.1226@compuserve.com>,
"P @ Draig Brady" <P@draigBrady.com>,
Ben Dooks <ben-linux@fluff.org>,
Dimitry Andric <dimitry.andric@tomtom.com>,
Olaf Hering <olh@suse.de>, Deepak Saxena <dsaxena@plexity.net>,
Christer Weinigel <wingel@nano-system.com>
Subject: Re: [WATCHDOG] v2.6.13 watchdog-patches
Date: Mon, 12 Sep 2005 13:28:19 -0400 [thread overview]
Message-ID: <4325BAB3.8090303@tmr.com> (raw)
In-Reply-To: <1125778302.3223.29.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sat, 2005-09-03 at 22:04 +0200, Wim Van Sebroeck wrote:
>
>>Author: Chuck Ebbert <76306.1226@compuserve.com>
>>Date: Fri Aug 19 14:14:07 2005 +0200
>>
>> [WATCHDOG] softdog-timer-running-oops.patch
>>
>> The softdog watchdog timer has a bug that can create an oops:
>>
>> 1. Load the module without the nowayout option.
>> 2. Open the driver and close it without writing 'V' before close.
>> 3. Unload the module. The timer will continue to run...
>> 4. Oops happens when timer fires.
>>
>> Reported Sun, 10 Oct 2004, by Michael Schierl <schierlm@gmx.de>
>>
>> Fix is easy: always take a reference on the module on open.
>> Release it only when the device is closed and no timer is running.
>> Tested on 2.6.13-rc6 using the soft_noboot option. While the
>> timer is running and the device is closed, the module use count
>> stays at 1. After the timer fires, it drops to 0. Repeatedly
>> opening and closing the driver caused no problems. Please apply.
>
>
>
> this looks ENTIRELY like the wrong solution!
> Isn't it a LOT easier to just del_timer_sync() the timer from the module
> exit code? Mucking with module refcounts in a driver is almost always a
> sign of a bug or at least really bad design, and I think that is the
> case here.....
>
Perhaps you misunderstood the problem. The problem is that the timer
module can be unloaded with a timer running. The solution is not to
silently stop the timer and allow the module to be unloaded, having a
timer running is, in a sense, a ref, and the ref count can and should
reflect that.
If the admin wants to stop the timer there are tools to do that now,
then the module can be removed.
I'm generally against the Windows approach of "do you really want to do
that?" paranoia about letting the user do certain things, but locking in
the module if I have started a timer sounds like a good safety precaution.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-09-12 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 20:04 [WATCHDOG] v2.6.13 watchdog-patches Wim Van Sebroeck
2005-09-03 20:11 ` Arjan van de Ven
2005-09-06 17:06 ` Josh Boyer
2005-09-06 21:41 ` Wim Van Sebroeck
2005-09-10 10:08 ` Arjan van de Ven
2005-09-12 17:28 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-03 22:44 Chuck Ebbert
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=4325BAB3.8090303@tmr.com \
--to=davidsen@tmr.com \
--cc=76306.1226@compuserve.com \
--cc=P@draigBrady.com \
--cc=arjan@infradead.org \
--cc=ben-linux@fluff.org \
--cc=dimitry.andric@tomtom.com \
--cc=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=torvalds@osdl.org \
--cc=wingel@nano-system.com \
/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