summaryrefslogtreecommitdiffstats
path: root/drivers/s390/sysinfo.c
diff options
context:
space:
mode:
authorChuck Ebbert <76306.1226@compuserve.com>2005-08-19 14:14:07 +0200
committerWim Van Sebroeck <wim@iguana.be>2005-09-03 13:59:46 +0200
commit1cc77248106aafc12ba529953f652d6f8db2c84d (patch)
tree6e5f8ee1053e7add2ec1890b594dc4086ae39f09 /drivers/s390/sysinfo.c
parent93642ecd463df30d032da8ac37c2676cee4ad876 (diff)
downloadblackbird-obmc-linux-1cc77248106aafc12ba529953f652d6f8db2c84d.tar.gz
blackbird-obmc-linux-1cc77248106aafc12ba529953f652d6f8db2c84d.zip
[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. Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com> Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Diffstat (limited to 'drivers/s390/sysinfo.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud