Revision 48cae885d5a896030588978f503c73c5ed5e62b1 authored by Stefan Weinhuber on 11 February 2009, 09:37:31 UTC, committed by Martin Schwidefsky on 11 February 2009, 09:37:40 UTC
In dasd_device_set_timer and dasd_block_set_timer we interpret the return value of mod_timer in a wrong way. If the timer expires in the small window between our check of timer_pending and the call to mod_timer, then the timer will be set, mod_timer returns zero and we will call add_timer for a timer that is already pending. As del_timer and mod_timer do all the necessary checking themselves, we can simplify our code and remove the race a the same time. Signed-off-by: Stefan Weinhuber <wein@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
1 parent ca0b4b7
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 860 bytes |
Makefile | -rw-r--r-- | 161 bytes |
README | -rw-r--r-- | 279 bytes |
bitmap.c | -rw-r--r-- | 3.6 KB |
dir.c | -rw-r--r-- | 2.5 KB |
file.c | -rw-r--r-- | 922 bytes |
fsync.c | -rw-r--r-- | 3.0 KB |
inode.c | -rw-r--r-- | 15.2 KB |
namei.c | -rw-r--r-- | 5.7 KB |
truncate.c | -rw-r--r-- | 727 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...