Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland

Hi Hugh,

On 10/12/07, Hugh Dickins <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
  - From: Hugh Dickins <[email protected]>

References:
- msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
  - From: Erez Zadok <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
  - From: Andrew Morton <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
  - From: "Ryan Finnie" <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
  - From: Hugh Dickins <[email protected]>

Prev by Date: [PATCH 01/10] remove dead code in pgtable_cache_init
Next by Date: Re: [PATCH] Allow kconfig to accept overrides
Previous by thread: Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
Next by thread: Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]