On Wed, 16 Sep 2009 09:39:40 +0800 Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote: > Silently ignore all vmalloc area holes in vread()/vwrite(), > and report success (or error code in future) to the caller. > > The original intention is to fix a vwrite() related bug, where > it could return 0 which cannot be handled correctly by its caller > write_kmem(). Then KAMEZAWA recommends to change the prototype > to make the semantics clear. > > CC: Andi Kleen <andi@xxxxxxxxxxxxxx> > CC: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> > CC: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> > CC: Ingo Molnar <mingo@xxxxxxx> > CC: Tejun Heo <tj@xxxxxxxxxx> > CC: Nick Piggin <npiggin@xxxxxxx> > CC: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> > Signed-off-by: Wu Fengguang <fengguang.wu@xxxxxxxxx> Okay, maybe it's good to change for now. I sometimes wonder we should use copy_to/from_user to access vmalloc area... but we have IO_REMAP. So, maybe vread/vwrite is required one. Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> Thanks, -Kame -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>