From owner-freebsd-hackers Tue Oct 29 10:53:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2C6B37B404 for ; Tue, 29 Oct 2002 10:53:41 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27E3643E42 for ; Tue, 29 Oct 2002 10:53:41 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9TIrbTx021161; Tue, 29 Oct 2002 10:53:37 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9TIrbSK021160; Tue, 29 Oct 2002 10:53:37 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 29 Oct 2002 10:53:37 -0800 From: David Schultz To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029185337.GA21064@HAL9000.homeunix.com> Mail-Followup-To: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG References: <20021029184724.A1682@gicco.homeip.net> <94802.1035914508@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94802.1035914508@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp : > >Isn't there a means to determine the state of the protection before > >the mount is attempted? > > As far as I know there isn't. I'm not sure if it is a device driver > (morituri te salutem!) or hardware issue. I believe most floppy drives can be queried for both their write-protect status and whether the inserted disk has been changed. If someone cared enough, these bits could be used to protect users from themselves. IMO, the retry-forever bug is the real problem, but I'm a bit skeptical that it's easy to solve safely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message