From: Todd Poynor <tpoynor@mvista.com>
To: linux-kernel@vger.kernel.org
Subject: BLKFLSBUF on ramdisks
Date: Wed, 26 May 2004 19:02:01 -0700 [thread overview]
Message-ID: <20040527020201.GC7176@slurryseal.ddns.mvista.com> (raw)
The BLKFLSBUF ioctl has a different meaning on ramdisks than on other
block devices: the memory for the ramdisk is freed (whereas cached
blocks are flushed to the device for most other devices, which obviously
would be a NOP for ramdisks). At least one command, freeramdisk of
BusyBox, expects this behavior. If certain other commands that issue
BLKFLSBUF are inadvertently run on a ramdisk device (as in a script that
previously tested fine on other devices) then the filesystem is
basically corrupted instead of the normally expected result. For
example, badblocks or e2fsck -F.
While this can be initially alarming, it is easily figured out and
avoided in the future (no one really needs to check bad blocks or
filesystem integrity on a ramdisk, and I'd assume other uses of the
ioctl would fall into a similar category). The two incompatible
definitions of the ioctl do seem unfortunate, however, and I figured I'd
ask here in case there's any interest in changing this situation; if so,
I will gladly help, thanks,
--
Todd
next reply other threads:[~2004-05-27 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 2:02 Todd Poynor [this message]
2004-05-27 19:47 ` [PATCH] " Theodore Ts'o
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=20040527020201.GC7176@slurryseal.ddns.mvista.com \
--to=tpoynor@mvista.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
all inboxes | Powered by JetHome®