public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: which dentry a page belongs to
Date: Fri, 23 Apr 2004 16:14:58 +0100	[thread overview]
Message-ID: <20040423151458.GC6300@mail.shareable.org> (raw)
In-Reply-To: <1082732223.1943.11.camel@zaphod>

Shaya Potter wrote:
> It would seem that since the
> address_space object contains the vm_area_struct's of i_mmap and
> i_mmap_shared I should then be able to get the appropriate file and
> dentry object's through
> 
> page->mapping->i_mmap->vm_file->f_dentry
> 
> or
> 
> page->mapping->i_mmap_shared->vm_file->f_dentry
> 
> 1) Is this correct logic?  I'm assuming the only things that matters in
> choosing which list is used if the page is map'd shared or not? is that
> correct as well?

No, no and no.

i_mmap and i_mmap_shared are lists.  They can both be empty, or both
non-empty.  A page can be mapped shared *and* non-shared at the same
time.  A page might not be mapped at all.

Also, a page is often mapped in a _subset_ of the mappings which are
found in i_mmap and i_mmap_shared: it depends on its offset, and the
vma offsets, and non-linear mapping offsets.

It is possible to find multiple dentries which are currently being
used to map a page.

It's also possible to find no dentries at all.

Your question is extremely ill-formed.  What do you mean by "the
dentry corresponding to a page"?  What do you want the value for?

-- Jamie

  reply	other threads:[~2004-04-23 15:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 14:57 which dentry a page belongs to Shaya Potter
2004-04-23 15:14 ` Jamie Lokier [this message]
2004-04-23 15:42   ` Shaya Potter
2004-04-23 16:37     ` Christoph Hellwig
2004-04-23 16:52       ` Shaya Potter
2004-04-23 17:01         ` Christoph Hellwig
2004-04-23 17:18           ` Shaya Potter
2004-04-23 17:22             ` Christoph Hellwig
2004-04-23 17:32               ` Shaya Potter
2004-04-23 17:37             ` Jamie Lokier
2004-04-23 17:59               ` Shaya Potter
2004-04-23 22:13                 ` Jamie Lokier
2004-04-23 18:05               ` Shaya Potter
2004-04-23 21:37                 ` Jamie Lokier
2004-04-23 22:26                   ` Shaya Potter
2004-04-23 22:49                     ` Jamie Lokier
2004-04-25  5:23                       ` Shaya Potter
2004-04-25 23:22                         ` Erez Zadok
2004-04-24  8:53           ` Jan Hudec
2004-04-24  8:44       ` Jan Hudec
2004-04-24  9:20         ` Christoph Hellwig
2004-04-24  9:32           ` Jan Hudec

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=20040423151458.GC6300@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=spotter@cs.columbia.edu \
    /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