mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Question regarding concurrent accesses through block device and  fs
Date: Thu, 12 Mar 2009 10:00:38 +0100	[thread overview]
Message-ID: <38b2ab8a0903120200h2f586c41s58d6a1520cba5ea8@mail.gmail.com> (raw)
In-Reply-To: <200903121922.53529.nickpiggin@yahoo.com.au>

On Thu, Mar 12, 2009 at 9:22 AM, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> Ignore details like crashes, direct IO and coherency between data mappings
> and buffercache where things get a bit hairy, and it's just a writeback
> cache. The last thing you write to some location will be what you get back
> if you read from that location -- regardless of whether it is dirty or clean
> or not present when you ask for it (and has to be read from disk).
>

Well yes but I was wondering in the special where the kernel crash or
the power supply is down how the kernel is minimizing the risk of file
system inconsistency. Hence my questions about metadata handling.

Thanks
-- 
Francis

  reply	other threads:[~2009-03-12  9:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2hc2yulrw.fsf@gmail.com>
2009-02-19 11:07 ` Francis Moreau
2009-02-19 13:44   ` Nick Piggin
2009-02-20 14:10     ` Francis Moreau
2009-02-23  3:58       ` Nick Piggin
2009-03-01 14:42         ` Francis Moreau
2009-03-01 15:32           ` Nick Piggin
2009-03-01 21:07             ` Francis Moreau
2009-03-02  7:11               ` Nick Piggin
2009-03-02 13:30                 ` Francis Moreau
2009-03-03  3:52                   ` Nick Piggin
2009-03-12  8:05                     ` Francis Moreau
2009-03-12  8:22                       ` Nick Piggin
2009-03-12  9:00                         ` Francis Moreau [this message]
2009-03-12  9:12                           ` Nick Piggin

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=38b2ab8a0903120200h2f586c41s58d6a1520cba5ea8@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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®