From: Mike Hayward <hayward@loup.net>
To: foosaa@gmail.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, jens.axboe@oracle.com,
linux-mm@kvack.org
Subject: Re: Linux kernel - Libata bad block error handling to user mode program
Date: Thu, 4 Mar 2010 09:37:55 -0700 [thread overview]
Message-ID: <201003041637.o24GbtJX005739@alien.loup.net> (raw)
In-Reply-To: <f875e2fe1003040458o3e13de97v3d839482939b687b@mail.gmail.com> (message from foo saa on Thu, 4 Mar 2010 07:58:07 -0500)
I always take it for granted, but forgot to mention, you should also
use O_DIRECT to bypass the linux buffer cache. It often gets in the
way of error propagation since it is changing your io requests into
it's own page sized ios and will also "lie" to you about having
written your data in the first place since it's a write back cache.
The point is you have to disable all the caches everywhere or the
error information will get absorbed by the caches.
- Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-03-04 16:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f875e2fe1003032052p944f32ayfe9fe8cfbed056d4@mail.gmail.com>
2010-03-04 6:42 ` Andrew Morton
2010-03-04 12:58 ` foo saa
2010-03-04 16:31 ` Mike Hayward
2010-03-04 18:12 ` s ponnusa
2010-03-05 0:42 ` Mike Hayward
2010-03-05 2:23 ` s ponnusa
2010-03-05 16:31 ` Mike Hayward
2010-03-05 6:01 ` Greg Freemyer
2010-03-05 13:04 ` Alan Cox
2010-03-04 16:37 ` Mike Hayward [this message]
2010-03-04 18:23 ` s ponnusa
2010-03-04 14:17 ` Greg Freemyer
2010-03-04 14:41 ` Mark Lord
2010-03-04 15:33 ` foo saa
2010-03-04 17:49 ` Mark Lord
2010-03-04 18:20 ` s ponnusa
2010-03-04 19:41 ` Greg Freemyer
2010-03-04 19:50 ` s ponnusa
2010-03-05 1:58 ` Robert Hancock
2010-03-05 2:11 ` s ponnusa
2010-03-05 2:16 ` Robert Hancock
2010-03-05 2:17 ` s ponnusa
2010-03-05 12:03 ` Alan Cox
2010-03-05 22:27 ` s ponnusa
2010-03-11 18:29 ` Greg Freemyer
2010-03-13 22:44 ` s ponnusa
2010-03-13 23:44 ` Robert Hancock
2010-03-14 0:12 ` s ponnusa
2010-03-14 5:06 ` Robert Hancock
2010-03-14 16:02 ` Mark Lord
2010-03-14 16:12 ` Greg Freemyer
2010-03-04 18:40 Kalra Ashish-B00888
2010-03-04 18:41 Kalra Ashish-B00888
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=201003041637.o24GbtJX005739@alien.loup.net \
--to=hayward@loup.net \
--cc=akpm@linux-foundation.org \
--cc=foosaa@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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