Stefan Richter a5c7f4710f firewire: insist on successive self ID complete events ... The whole topology code only works if the old and new topologies which are compared come from immediately successive self ID complete events. If there happened bus resets without self ID complete events in the meantime, or self ID complete events with invalid selfIDs, the topology comparison could identify nodes wrongly, or more likely just corrupt kernel memory or panic right away. We now discard all nodes of the old topology and treat all current nodes as new ones if the current self ID generation is not the previous one plus 1. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by: Jarod Wilson <jwilson@redhat.com>		2009-01-20 19:29:51 +01:00
..
fw-card.c	firewire: core: fix sleep in atomic context due to driver core change	2009-01-09 23:22:32 +01:00
fw-cdev.c	firewire: fix ioctl() return code	2008-10-15 22:21:10 +02:00
fw-device.c	firewire: core: fix sleep in atomic context due to driver core change	2009-01-09 23:22:32 +01:00
fw-device.h	firewire: fix small memory leak at module removal	2009-01-04 23:50:37 +01:00
fw-iso.c
fw-ohci.c	firewire: fw-ohci: fix IOMMU resource exhaustion	2008-12-10 12:45:34 +01:00
fw-ohci.h
fw-sbp2.c	firewire: fw-sbp2: remove unnecessary locking	2009-01-04 23:50:36 +01:00
fw-topology.c	firewire: insist on successive self ID complete events	2009-01-20 19:29:51 +01:00
fw-topology.h
fw-transaction.c	firewire: fix small memory leak at module removal	2009-01-04 23:50:37 +01:00
fw-transaction.h	firewire: reorder struct fw_card for better cache efficiency	2009-01-04 23:50:38 +01:00
Kconfig	firewire: Kconfig help update	2008-08-19 18:47:56 +02:00
Makefile