From: Pavel Machek <pavel@suse.cz>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: data corruption: revalidating a (removable) hdd/flash on re-insert
Date: Tue, 4 Nov 2008 21:20:11 +0100 [thread overview]
Message-ID: <20081104202011.GA7135@ucw.cz> (raw)
In-Reply-To: <ac3eb2510811041213l4a20fa12h3c5beb3c2d317574@mail.gmail.com>
> >> Every access to removable media is guarded by this revalidation check.
> >> If you don't see these events, you should not trust this reader, and
> >> at least never change the media while it is connected.
> >
> > This is rather nasty data-corrupter.
>
> Sure, it is.
>
> > Could we at least blacklist
> > broken device, and force revalidation on each close or something like
> > that?
>
> What's your idea of revalidation if the hardware does not tell you?
> Get an md5 of the disk content? :)
Well... you should not eject media while fs is mounted or blockdev is
open, correct?
So can we simply claim 'media changed' on last close/unmount? Sure,
sometimes media was not changed, but that only hurts performance, not
correctness... ?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-11-04 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 15:38 data corruption: revalidating a (removable) hdd/flash on re-insert Michael Tokarev
2008-10-31 15:59 ` Lennart Sorensen
2008-10-31 16:10 ` Michael Tokarev
2008-10-31 18:28 ` Lennart Sorensen
2008-10-31 16:10 ` Kay Sievers
2008-10-31 17:39 ` Michael Tokarev
2008-10-31 18:49 ` Kay Sievers
2008-11-04 19:57 ` Pavel Machek
2008-11-04 20:13 ` Kay Sievers
2008-11-04 20:20 ` Pavel Machek [this message]
2008-11-04 21:22 ` Michael Tokarev
2008-11-04 21:28 ` Pavel Machek
2008-11-05 8:04 ` Michael Tokarev
2008-11-05 0:29 ` Kay Sievers
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=20081104202011.GA7135@ucw.cz \
--to=pavel@suse.cz \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.