Hi, On 10/26/07, Neil Brown <[email protected]> wrote: > It seems that the new requirement is that if the address_space > chooses not to write out the page, it should now call SetPageActive(). > If that is the case, I think it should be explicit in the > documentation - please? Agreed. - 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/
- References:
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- From: Pekka J Enberg <[email protected]>
- Re: 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: "Pekka Enberg" <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- From: Hugh Dickins <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- From: "Pekka Enberg" <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- From: Hugh Dickins <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- From: Neil Brown <[email protected]>
- Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- Prev by Date: Re: msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland
- Next by Date: [PATCH] De-constify sched.h
- 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):
 |