All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: File and device pages and buffers
Date: Thu, 21 Apr 2005 22:16:08 +0200	[thread overview]
Message-ID: <8e70aacf0504211316b57ce71@mail.gmail.com> (raw)
In-Reply-To: <8e70aacf05041717093deeb825@mail.gmail.com>

Can I try to bring your attention once more to the following issue:

On 4/18/05, Martin Jambor <jamborm@gmail.com> wrote:
> There is one thing about cache pages and buffers that puzzles me and
> that I have not found in any documenatation and that is not quite
> obvious from the source.
> 
> What is the relationship between:
> a) pages and their buffers associated with the device (typically
> bh->bdev->bd_inode and its mapping) and
> 
> b) pages and their buffers associated with files on that device.
> 
> Can anyone tell me  what the relationship exactly is and what one has
> to be aware of when manipulating either of these?

My conclusion from reading the source is that after mapping a file
buffer (buffer belonging to a page that is a part of a file on a
device) to a particular block on a device, one should call
unmap_underlying_metadata to make sure any writing using a device
buffer will not overwrite the file. And that one must not use device
buffers to write to places which have been mapped to files.

Is that correct?

TIA

Martin

      reply	other threads:[~2005-04-21 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18  0:09 File and device pages and buffers Martin Jambor
2005-04-21 20:16 ` Martin Jambor [this message]

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=8e70aacf0504211316b57ce71@mail.gmail.com \
    --to=jamborm@gmail.com \
    --cc=linux-fsdevel@vger.kernel.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 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.