mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NTFS safety and lack thereof - Was: Re: Linux 2.4.0ac11
Date: Wed, 24 Jan 2001 17:23:49 +0000	[thread overview]
Message-ID: <5.0.2.1.2.20010124170609.00a0c190@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20010124170337Z129710-18594+930@vger.kernel.org>
In-Reply-To: <5.0.2.1.2.20010124162842.00a48720@pop.cus.cam.ac.uk> <E14LOAm-0006z0-00@the-village.bc.nu> <E14LOAm-0006z0-00@the-village.bc.nu> <01012416081105.19999@nessie>

At 17:03 24/01/01, Timur Tabi wrote:
>** Reply to message from Anton Altaparmakov <aia21@cam.ac.uk> on Wed, 24 Jan
>2001 16:54:36 +0000
>
> > >Is read access safe ?
> >
> > Of course read-only is safe. As long as you mount the partition READ-ONLY
> > nothing can happen to it in any way, your NTFS data is at least safe.
>
>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?

Theoretically it is also possible that all quantums in my body decide to 
tunnel through space-time at exactly the same time and with the exactly 
same direction and speed vector for exactly the same duration of time and 
that I am suddenly effectively teleported to the surface of the moon. (-:

But that doesn't mean it's going to happen...

Seriously, it is a theoretical possibility but a practical impossibility in 
my opinion and to the best of my knowledge of the current driver it will 
not communicate with any hardware directly in any way. In fact it only 
performs writes by dirtying buffer cache buffers which get written back by 
the kernel proper. ll_rw_block() never gets called directly and neither 
does generic_make_request() and block_write_full_page() isn't at the moment 
either. (Anything I missed?) Also, when you compile the driver without the 
write support enabled, you are almost 100% sure even a major bug in the 
driver will not cause any writes.

And no, the driver is not a virus nor a trojan nor does it have any 
intelligence to suddenly decide to write things when it isn't asked to...

NOTE: Please don't take my comments personally / too seriously but I 
couldn't resist... Follow-ups to alt.silly.* please...

Regards,

         Anton


-- 
      "Education is what remains after one has forgotten everything he 
learned in school." - Albert Einstein
-- 
Anton Altaparmakov  Voice: +44-(0)1223-333541(lab) / +44-(0)7712-632205(mobile)
Christ's College    eMail: AntonA@bigfoot.com / aia21@cam.ac.uk
Cambridge CB2 3BU    ICQ: 8561279
United Kingdom       WWW: http://www-stu.christs.cam.ac.uk/~aia21/

-
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/

  parent reply	other threads:[~2001-01-24 17:24 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
2001-01-26 17:38       ` Pavel Machek
2001-01-24 17:23     ` Anton Altaparmakov [this message]
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=5.0.2.1.2.20010124170609.00a0c190@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttabi@interactivesi.com \
    /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®