From: "Greg Freemyer" <greg.freemyer@gmail.com>
To: "Sitsofe Wheeler" <sitsofe@yahoo.com>
Cc: "Mark Lord" <liml@rtr.ca>, Redeeman <redeeman@metanurb.dk>,
piergiorgio.sartor@nexgo.de, neilb@suse.de,
linux-raid@vger.kernel.org,
"IDE/ATA development list" <linux-ide@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: detection of silent corruption via ATA long sector reads
Date: Fri, 2 Jan 2009 16:05:48 -0500 [thread overview]
Message-ID: <87f94c370901021305x7ad237ear25dcd32cbe6e7d2c@mail.gmail.com> (raw)
In-Reply-To: <124360.23007.qm@web110612.mail.gq1.yahoo.com>
On Fri, Jan 2, 2009 at 3:43 PM, Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
>> Is there a more comprehensive write-up / resource that describes the
>> current status of the overall INTEGRITY support is, especially as it
>> relates to ATA devices?
>
>
> Did you check the kernel notes on kernelnewbies when the feature went in -
> http://kernelnewbies.org/Linux_2_6_27 ?
Interesting read, but it does not really answer the questions I posed.
I did look through the 2.6.27 source I have handy and the only call to
blk_integrity_register() is in./drivers/scsi/sd_dif.c.
That leaves me with the impression that there are not any ATA devices
claiming support yet.
Greg
--
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
next prev parent reply other threads:[~2009-01-02 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.8mwKV7y4hm+Q6mvIKtp9QGoJYUU@ifi.uio.no>
[not found] ` <fa.4QcsYZC0gJJwJ0eUOht3hDYaVWs@ifi.uio.no>
[not found] ` <49580061.9060506@yahoo.com>
[not found] ` <87f94c370901021226j40176872h9e5723c6da4afcbe@mail.gmail.com>
2009-01-02 20:43 ` Sitsofe Wheeler
2009-01-02 21:05 ` Greg Freemyer [this message]
2008-12-26 21:44 Greg Freemyer
2008-12-26 22:15 ` Robert Hancock
2008-12-28 22:26 ` Mark Lord
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=87f94c370901021305x7ad237ear25dcd32cbe6e7d2c@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=piergiorgio.sartor@nexgo.de \
--cc=redeeman@metanurb.dk \
--cc=sitsofe@yahoo.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
Powered by JetHome