[PATCH 0/4] firewire: order of memory accesses (bus generation vs.node ID)

From: Stefan Richter
Date: Wed Jan 23 2008 - 19:53:30 EST


I now updated some patches from November according to comments I
received from Nick back then. As Jarod found out now while testing the
November versions, parts of these patches actually fix multiply reported
bugs.

While updating this stuff, I also found two more read sites where the
read order was not properly enforced.

Incoming:
1/4 firewire: fw-sbp2: use device generation, not card generation
2/4 firewire: fw-cdev: use device generation, not card generation
3/4 firewire: enforce access order between generation and node ID
4/4 firewire: fw-core: react on bus resets while the config ROM is being fetched

drivers/firewire/fw-cdev.c | 3 ++-
drivers/firewire/fw-device.c | 33 ++++++++++++++++++++++++---------
drivers/firewire/fw-device.h | 12 ++++++++++++
drivers/firewire/fw-sbp2.c | 14 ++++++++------
drivers/firewire/fw-topology.c | 5 +++++
5 files changed, 51 insertions(+), 16 deletions(-)
--
Stefan Richter
-=====-==--- ---= ==---
http://arcgraph.de/sr/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/