linux-kernel - Re: [PATCH] firewire: fw-ohci: catch self_id

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47E4DD50.9050706@s5r6.in-berlin.de>
Date:	Sat, 22 Mar 2008 11:20:00 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	linux1394-devel@...ts.sourceforge.net
CC:	Jarod Wilson <jwilson@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firewire: fw-ohci: catch self_id_count == 0

Stefan Richter wrote:
> fw_core_handle_bus_reset() incorrectly relied on the assumption that
> self_id_count > 0.

Even though
     firewire: insist on successive self ID complete events
     firewire: fw-ohci: add self ID error check
     firewire: fw-ohci: catch self_id_count == 0
didn't fix any of Jarod's weird setups, I plan on submitting these 
patches nevertheless (after 2.6.25) because they IMO fix real 
possibilities for panics in the topology code.
-- 
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/