| 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.abda19e1774a3da3@s5r6.in-berlin.de> Date: Sat, 16 Feb 2008 16:51:55 +0100 (CET) From: Stefan Richter <stefanr@...6.in-berlin.de> To: Jarod Wilson <jwilson@...hat.com>, Kristian Hoegsberg <krh@...planet.net> cc: linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH 9/9] firewire: fw-sbp2: fix I/O errors during reconnect I wrote: > The only remedy seems to be to block the SCSI device until reconnect. In the longer term, we should look into keeping commands enqueued in fw-sbp2 during the reconnect phase. Plus we need full parallelism of sbp2_reconnect and sbp2_login between all attached targets. The current single-threaded scheme does not work too well for more than one target attached to the same bus. The old stack handles that case in a single thread too but is better tuned to sbp2's needs. The old stack blocks the Scsi_Hosts earlier, guaranteedly performs all reconnects and re-logins before any new login, and has a small delay between self-ID-complete and reconnect. I looked into changing fw-sbp2's own workqueue delays and into adding a counter to fw-sbp2 to track outstanding reconnects in order to defer new logins, but it is too messy. -- 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