All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Hugh Dickins <hugh@veritas.com>
Cc: Stefani Seibold <stefani@seibold.net>,
	Jaya Kumar <jayakumar.lkml@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
	linux-mm@kvack.org
Subject: Re: vm_ops.page_mkwrite() fails with vmalloc on 2.6.23
Date: Tue, 30 Oct 2007 14:12:38 +0100	[thread overview]
Message-ID: <1193749958.27652.77.camel@twins> (raw)
In-Reply-To: <Pine.LNX.4.64.0710301232220.9601@blonde.wat.veritas.com>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

On Tue, 2007-10-30 at 12:39 +0000, Hugh Dickins wrote:
> On Tue, 30 Oct 2007, Stefani Seibold wrote:
> > 
> > the question is how can i get all pte's from a vmalloc'ed memory. Due to
> > the zeroed mapping pointer i dont see how to do this?
> 
> The mapping pointer is zeroed because you've done nothing to set it.
> Below is how I answered you a week ago.  But this is new territory
> (extending page_mkclean to work on more than just pagecache pages),
> I'm still unsure what would be the safest way to do it.

Quite, I think manual usage of page_mkclean_one() on the vma gotten from
mmap() along with properly setting page->index is the simplest solution
to make work.

Making page_mkclean(struct page *) work for remap_pfn/vmalloc_range()
style mmaps would require extending rmap to work with those, which
includes setting page->mapping to point to a anon_vma like object.

But that sounds like a lot of work, and I'm not sure its worth the
overhead, because so far all users of remap_pfn/vmalloc_range() have
survived without.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-10-30 13:12 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 14:40 vm_ops.page_mkwrite() fails with vmalloc on 2.6.23 Stefani Seibold
2007-10-29  7:40 ` Andrew Morton
2007-10-29  7:40   ` Andrew Morton
2007-10-29  8:17   ` Jaya Kumar
2007-10-29  8:17     ` Jaya Kumar
2007-10-29 10:11     ` Peter Zijlstra
2007-10-29 10:11       ` Peter Zijlstra
2007-10-29 12:35       ` Peter Zijlstra
2007-10-29 12:35         ` Peter Zijlstra
2007-10-29 14:28         ` Nick Piggin
2007-10-29 14:28           ` Nick Piggin
2007-10-29 17:01     ` Peter Zijlstra
2007-10-29 17:01       ` Peter Zijlstra
2007-10-29 17:51       ` Jaya Kumar
2007-10-29 17:51         ` Jaya Kumar
2007-10-29 18:17         ` Peter Zijlstra
2007-10-29 18:17           ` Peter Zijlstra
2007-10-29 22:16           ` Peter Zijlstra
2007-10-29 22:16             ` Peter Zijlstra
2007-10-30  1:22             ` Jaya Kumar
2007-10-30  1:22               ` Jaya Kumar
2007-10-30  9:56               ` Peter Zijlstra
2007-10-30 10:49                 ` Stefani Seibold
2007-10-30 10:49                   ` Stefani Seibold
2007-10-30 12:39                   ` Hugh Dickins
2007-10-30 12:39                     ` Hugh Dickins
2007-10-30 13:12                     ` Peter Zijlstra [this message]
2007-10-30 13:16                 ` Jaya Kumar
2007-10-30 13:16                   ` Jaya Kumar
2007-10-30 13:25                   ` Peter Zijlstra
2007-10-30 15:47                     ` Hugh Dickins
2007-10-30 15:47                       ` Hugh Dickins
2007-10-30 15:51                       ` Peter Zijlstra
2007-11-01  8:02                       ` Jaya Kumar
2007-11-01  8:02                         ` Jaya Kumar
  -- strict thread matches above, loose matches on Subject: below --
2007-10-22 14:45 Stefani Seibold
2007-10-22 16:37 ` Hugh Dickins
2007-10-22 17:03   ` Jaya Kumar
2007-10-22 17:17 ` Peter Zijlstra
2007-10-22 17:20   ` Peter Zijlstra

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=1193749958.27652.77.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=hugh@veritas.com \
    --cc=jayakumar.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=stefani@seibold.net \
    /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.