public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Writes to mounted devices containing file-systems.
Date: 11 Aug 2001 12:16:23 -0700	[thread overview]
Message-ID: <9l40a7$9ja$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010810075750.10479A-100000@chaos.analogic.com> <20010811144729.B31614@wyvern>

Followup to:  <20010811144729.B31614@wyvern>
By author:    Adrian Bridgett <adrian.bridgett@iname.com>
In newsgroup: linux.dev.kernel
> 
> Personally I'd prefer AIX's approach - let the write through (if the user
> wants to shoot themselves in the foot...), but report an error about it (to
> syslog). 
> 

I don't see any point in having "you just fscked yourself" written to
the syslog.  At the same time, writing to a mounted device is actually
useful: it's currently the only way to write the boot block on an
ext2 filesystem (and Viro: if you start using the page cache for the
superblock in ext2, you probably have to add an explicit interface to
write the boot block at the same time!!!)

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

      reply	other threads:[~2001-08-11 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10 12:43 Writes to mounted devices containing file-systems Richard B. Johnson
2001-08-10 13:07 ` Alan Cox
2001-08-10 13:23 ` Helge Hafting
2001-08-10 13:56 ` Anton Altaparmakov
2001-08-10 14:22   ` Matt
2001-08-10 18:04 ` Steve VanDevender
2001-08-10 19:18 ` Alexander Viro
2001-08-11 12:28   ` Kai Henningsen
2001-08-10 19:21 ` H. Peter Anvin
2001-08-11 13:47 ` Adrian Bridgett
2001-08-11 19:16   ` H. Peter Anvin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='9l40a7$9ja$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox