From: "mirabilos" <eccesys@topmail.de>
To: "Linux-Kernel ML" <linux-kernel@vger.kernel.org>
Subject: Re: NTFS safety and lack thereof - Was: Re: Linux 2.4.0ac11
Date: Wed, 24 Jan 2001 17:09:49 -0000 [thread overview]
Message-ID: <008f01c08629$f2582d20$0100a8c0@homeip.net> (raw)
In-Reply-To: <E14LOAm-0006z0-00@the-village.bc.nu> <E14LOAm-0006z0-00@the-village.bc.nu> <01012416081105.19999@nessie> <20010124170337Z129710-18594+930@vger.kernel.org>
Timur Tabi wrote:
> Isn't it still theoretcially possible for the driver to send commands to the
> disk controller that cause data to become overwritten, even when it's just
> supposed to read that data?
IMHO the NTFS driver creators weren't bloody newbies and won't do such
a bug, even not by accidence.
Also I think there might be a VFS protection of R/O space, but I'm not sure.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 17:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.31ksi3.0101241721470.605-100000@nomad.cyberbill s.com>
2001-01-24 11:33 ` Alan Cox
2001-01-24 15:05 ` Cataldo Thomas
2001-01-24 17:03 ` NTFS safety and lack thereof - Was: " Timur Tabi
2001-01-24 17:09 ` mirabilos [this message]
2001-01-26 17:38 ` Pavel Machek
2001-01-24 17:23 ` Anton Altaparmakov
2001-01-24 16:54 ` Anton Altaparmakov
2001-01-24 20:06 ` Luc de Louw
2001-01-25 1:36 ` Alan Cox
2001-01-25 1:39 ` Sergey Kubushin
2001-01-25 5:18 ` Andre Hedrick
2001-01-25 11:02 ` Matthias Andree
2001-01-25 16:50 ` Sergey Kubushin
2001-01-25 2:04 ` Anton Altaparmakov
2001-01-25 2:13 ` Sergey Kubushin
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='008f01c08629$f2582d20$0100a8c0@homeip.net' \
--to=eccesys@topmail.de \
--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®