linux-kernel - Re: [PATCH 9/9] firewire: fw-sbp2: fix I/O errors during reconnect

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]

Date:	Tue, 12 Feb 2008 09:01:27 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Jarod Wilson <jwilson@...hat.com>
CC:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 9/9] firewire: fw-sbp2: fix I/O errors during reconnect

Jarod Wilson wrote:
> Stefan Richter wrote:
>> "perceived" unplugs can happen if a third node is slowly plugged in or out
[...]
> I wonder if there's any sort of
> guidance on this sort of thing in the firewire specs...

I am not aware of any.

The hardware related parts of the 1394a PHY layer spec have AFAIR
enhancements over 1394-1995 to avoid bursts of bus reset events when
connectors scrape into or out of the ports.  But what I saw on a few
occasions now were proper self ID complete events, not merely bus reset
events.  (The firewire stack only cares for self ID complete, therefore
multiple bus reset events before one self ID complete event aren't a
problem in the first place.  I don't know though whether these bursts of
bus resets which 1394a addressed had self ID complete events in them or
not.)
-- 
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/