| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <tkrat.288da3bd61ecfb20@s5r6.in-berlin.de> Date: Thu, 24 Jan 2008 01:52:25 +0100 (CET) From: Stefan Richter <stefanr@...6.in-berlin.de> To: linux1394-devel@...ts.sourceforge.net cc: linux-kernel@...r.kernel.org, Kristian Høgsberg <krh@...hat.com>, Jarod Wilson <jwilson@...hat.com>, Nick Piggin <nickpiggin@...oo.com.au> Subject: [PATCH 0/4] firewire: order of memory accesses (bus generation vs. node ID) 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists