linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Nick Piggin <npiggin@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
	Hugh Dickins <hugh.dickins@tiscali.co.uk>,
	Christoph Lameter <cl@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH 5/8] vmalloc: simplify vread()/vwrite()
Date: Thu, 21 Jan 2010 13:05:21 +0800	[thread overview]
Message-ID: <20100121050521.GB24236@localhost> (raw)
In-Reply-To: <20100119112343.04f4eff5.kamezawa.hiroyu@jp.fujitsu.com>

On Mon, Jan 18, 2010 at 07:23:43PM -0700, KAMEZAWA Hiroyuki wrote:
> On Tue, 19 Jan 2010 09:33:03 +0800
> Wu Fengguang <fengguang.wu@intel.com> wrote:
> > > The whole thing looks stupid though, apparently kmap is used to avoid "the
> > > lock". But the lock is already held. We should just use the vmap
> > > address.
> > 
> > Yes. I wonder why Kame introduced kmap_atomic() in d0107eb07 -- given
> > that he at the same time fixed the order of removing vm_struct and
> > vmap in dd32c279983b.
> > 
> Hmm...I must check my thinking again before answering..
> 
> vmalloc/vmap is constructed by 2 layer.
> 	- vmalloc layer....guarded by vmlist_lock.
> 	- vmap layer   ....gurderd by purge_lock. etc.
> 
> Now, let's see how vmalloc() works. It does job in 2 steps.
> vmalloc():
>   - allocate vmalloc area to the list under vmlist_lock.
> 	- map pages.
> vfree()
>   - free vmalloc area from the list under vmlist_lock.
> 	- unmap pages under purge_lock.
> 
> Now. vread(), vwrite() just take vmlist_lock, doesn't take purge_lock().
> It walks page table and find pte entry, page, kmap and access it.
> 
> Oh, yes. It seems it's safe without kmap. But My concern is percpu allocator.
> 
> It uses get_vm_area() and controls mapped pages by themselves and
> map/unmap pages by with their own logic. vmalloc.c is just used for
> alloc/free virtual address. 
> 
> Now, vread()/vwrite() just holds vmlist_lock() and walk page table
> without no guarantee that the found page is stably mapped. So, I used kmap.
> 
> If I miss something, I'm very sorry to add such kmap.

Ah Thanks for explanation!

I did some audit and find that

- set_memory_uc(), set_memory_array_uc(), set_pages_uc(),
  set_pages_array_uc() are called EFI code and various video drivers,
  all of them don't touch HIGHMEM RAM

- Kame: ioremap() won't allow remap of physical RAM

So kmap_atomic() is safe.  Let's just settle on this patch?

Thanks,
Fengguang

--
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>

  reply	other threads:[~2010-01-21  5:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 13:53 [PATCH 0/8] devmem/kmem/kcore fixes, cleanups and hwpoison checks Wu Fengguang
2010-01-13 13:53 ` [PATCH 1/8] vfs: fix too big f_pos handling Wu Fengguang
2010-01-13 13:53 ` [PATCH 2/8] devmem: check vmalloc address on kmem read/write Wu Fengguang
2010-01-13 13:53 ` [PATCH 3/8] devmem: fix kmem write bug on memory holes Wu Fengguang
2010-01-13 13:53 ` [PATCH 4/8] resources: introduce generic page_is_ram() Wu Fengguang
2010-01-13 14:29   ` Américo Wang
2010-01-14  3:29     ` Wu Fengguang
2010-01-13 13:53 ` [PATCH 5/8] vmalloc: simplify vread()/vwrite() Wu Fengguang
2010-01-14 12:45   ` Nick Piggin
2010-01-18 13:35     ` Wu Fengguang
2010-01-18 14:23       ` Nick Piggin
2010-01-19  1:33         ` Wu Fengguang
2010-01-19  2:23           ` KAMEZAWA Hiroyuki
2010-01-21  5:05             ` Wu Fengguang [this message]
2010-01-21  5:21               ` KAMEZAWA Hiroyuki
2010-01-21  5:49                 ` Wu Fengguang
2010-01-13 13:53 ` [PATCH 6/8] hwpoison: prevent /dev/kmem from accessing hwpoison pages Wu Fengguang
2010-01-13 13:53 ` [PATCH 7/8] hwpoison: prevent /dev/mem " Wu Fengguang
2010-01-13 13:53 ` [PATCH 8/8] hwpoison: prevent /dev/kcore " Wu Fengguang
2010-01-13 14:23   ` Américo Wang

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=20100121050521.GB24236@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=cl@linux-foundation.org \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).