From: Nick Piggin Clarify that preemption needs to be guarded against with the __xxx_page_state functions. Signed-off-by: Nick Piggin Signed-off-by: Andrew Morton --- include/linux/page-flags.h | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff -puN include/linux/page-flags.h~mm-page_state-comment-more include/linux/page-flags.h --- devel/include/linux/page-flags.h~mm-page_state-comment-more 2006-01-23 00:22:53.000000000 -0800 +++ devel-akpm/include/linux/page-flags.h 2006-01-23 00:22:53.000000000 -0800 @@ -86,8 +86,9 @@ * - The __xxx_page_state variants can be used safely when interrupts are * disabled. * - The __xxx_page_state variants can be used if the field is only - * modified from process context, or only modified from interrupt context. - * In this case, the field should be commented here. + * modified from process context and protected from preemption, or only + * modified from interrupt context. In this case, the field should be + * commented here. */ struct page_state { unsigned long nr_dirty; /* Dirty writeable pages */ _