mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-18 17:54:13 +08:00
f8d2dc3938
read_rom() obtained a fresh new fw_device.generation for each read transaction. Hence it was able to continue reading in the middle of the ROM even if a bus reset happened. However the device may have modified the ROM during the reset. We would end up with a corrupt fetched ROM image then. Although all of this is quite unlikely, it is not impossible. Therefore we now restart reading the ROM if the bus generation changed. Note, the memory barrier in read_rom() is still necessary according to tests by Jarod Wilson, despite of the ->generation access being moved up in the call chain. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> This is essentially what I've been beating on locally, and I've yet to hit another config rom read failure with it. Signed-off-by: Jarod Wilson <jwilson@redhat.com> |
||
|---|---|---|
| .. | ||
| fw-card.c | ||
| fw-cdev.c | ||
| fw-device.c | ||
| fw-device.h | ||
| fw-iso.c | ||
| fw-ohci.c | ||
| fw-ohci.h | ||
| fw-sbp2.c | ||
| fw-topology.c | ||
| fw-topology.h | ||
| fw-transaction.c | ||
| fw-transaction.h | ||
| Kconfig | ||
| Makefile | ||