7baeb6a5cc
I found a bug in the packet writing driver that could cause data corruption. The problem arised if the driver got a write request for a sector in a "zone" it was already working on. In that case it was supposed to queue the write request until it was done processing earlier requests for the same zone, and instead work on some other zone in the mean time. However, if there was no other zone to work on, the driver would initiate two packet_data objects for the same zone, causing unpredictable things to happen. Signed-off-by: Peter Osterlund <petero2@telia.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> |
||
|---|---|---|
| .. | ||
| aoe | ||
| paride | ||
| acsi_slm.c | ||
| acsi.c | ||
| amiflop.c | ||
| as-iosched.c | ||
| ataflop.c | ||
| cciss_cmd.h | ||
| cciss_scsi.c | ||
| cciss_scsi.h | ||
| cciss.c | ||
| cciss.h | ||
| cfq-iosched.c | ||
| cpqarray.c | ||
| cpqarray.h | ||
| cryptoloop.c | ||
| DAC960.c | ||
| DAC960.h | ||
| deadline-iosched.c | ||
| elevator.c | ||
| floppy.c | ||
| genhd.c | ||
| ida_cmd.h | ||
| ida_ioctl.h | ||
| ioctl.c | ||
| Kconfig | ||
| Kconfig.iosched | ||
| ll_rw_blk.c | ||
| loop.c | ||
| Makefile | ||
| nbd.c | ||
| noop-iosched.c | ||
| pktcdvd.c | ||
| ps2esdi.c | ||
| rd.c | ||
| scsi_ioctl.c | ||
| smart1,2.h | ||
| swim3.c | ||
| swim_iop.c | ||
| sx8.c | ||
| ub.c | ||
| umem.c | ||
| viodasd.c | ||
| xd.c | ||
| xd.h | ||
| z2ram.c | ||