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
| ||
|
Date: Tue, 28 Dec 2010 11:41:58 +0100 From: torn5 <torn5@...ftmail.org> To: linux-ext4@...r.kernel.org, "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org> Subject: Ext4 and scsi commands resubmission Hello all, in open-iscsi, when network connectivity is lost, scsi commands that were in-flight at the moment of disconnection are failed to the SCSI layer. These get resubmitted up to 5 times by the SCSI layer (or so is written in the open-iscsi docs) and after that they are held in the queue (device "blocked") until the network connection is restored. Now the question is: when SCSI resubmits commands to a device, I suppose they go to the end of the queue for the device, and not at the head like they were. Am I right? How do filesystems, and in particular ext4, react to that? I suppose the ordering goes awry, barriers cannot succeed in this way, especially if they were submitted as real SCSI barriers (i.e. without using flush + command + flush workaround) Thank you -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists