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: Wed, 3 Dec 2008 19:16:05 +0100 From: Pavel Machek <pavel@...e.cz> To: Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Theodore Tso <tytso@....edu>, Chris Friesen <cfriesen@...tel.com>, kernel list <linux-kernel@...r.kernel.org>, aviro@...hat.com Subject: Re: writing file to disk: not as easy as it looks > > CRC errors, lost IRQs and the like are retried by the midlayer and > > drivers and the error handling strategies will also try things like > > reducing link speeds on repeated CRC errors. > > I meant for example loose cable or so --- does it make sense to retry > indefinitely (until the admin plugs the cable or unmounts the filesystem) > or return error to the filesystem after few retries? It is quite non-trivial to detect if it is "disk plugged back in" vs. "faulty disk unplugged, new one plugged in"... so I suppose automatic retry after failure of connection to disk is quite hard to get right. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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