[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100121054932.GD24236@localhost>
Date: Thu, 21 Jan 2010 13:49:32 +0800
From: Wu Fengguang <fengguang.wu@...el.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: Nick Piggin <npiggin@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, Tejun Heo <tj@...nel.org>,
Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Christoph Lameter <cl@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [PATCH 5/8] vmalloc: simplify vread()/vwrite()
On Wed, Jan 20, 2010 at 10:21:06PM -0700, KAMEZAWA Hiroyuki wrote:
> On Thu, 21 Jan 2010 13:05:21 +0800
> Wu Fengguang <fengguang.wu@...el.com> wrote:
>
> > On Mon, Jan 18, 2010 at 07:23:43PM -0700, KAMEZAWA Hiroyuki wrote:
> > 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?
> >
> I recommend you to keep check on VM_IOREMAP. That was checked far before
> I started to see Linux. Some _unknown_ driver can call get_vm_area() and
> map arbitrary pages there.
OK, I'll turn this patch into a less radical one.
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists