Messages in this thread | | | Date | Sat, 13 Oct 2007 00:45:48 +0300 | From | "Pekka Enberg" <> | Subject | Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland |
| |
Hi Hugh,
On 10/12/07, Hugh Dickins <hugh@veritas.com> wrote: > But I keep suspecting that the answer might be the patch below (which > rather follows what drivers/block/rd.c is doing). I'm especially > worried that, rather than just AOP_WRITEPAGE_ACTIVATE being returned > to userspace, bad enough in itself, you might be liable to hit that > BUG_ON(page_mapped(page)). shmem_writepage does not expect to be > called by anyone outside mm/vmscan.c, but unionfs can now get to it?
Doesn't msync(2) get to it via mm/page-writeback.c:write_cache_pages() without unionfs even?
Pekka - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |