From: Christoph Lameter <cl@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Russ Anderson <rja@sgi.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Dave Jones <davej@redhat.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/8] badpage: simplify page_alloc flag check+clear
Date: Mon, 1 Dec 2008 08:47:22 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.64.0812010843230.15331@quilx.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812010038220.11401@blonde.site>
On Mon, 1 Dec 2008, Hugh Dickins wrote:
> /*
> * Flags checked when a page is freed. Pages being freed should not have
> * these flags set. It they are, there is a problem.
> */
> -#define PAGE_FLAGS_CHECK_AT_FREE (PAGE_FLAGS | 1 << PG_reserved)
> +#define PAGE_FLAGS_CHECK_AT_FREE \
> + (1 << PG_lru | 1 << PG_private | 1 << PG_locked | \
> + 1 << PG_buddy | 1 << PG_writeback | 1 << PG_reserved | \
> + 1 << PG_slab | 1 << PG_swapcache | 1 << PG_active | \
> + __PG_UNEVICTABLE | __PG_MLOCKED)
Rename this to PAGE_FLAGS_CLEAR_WHEN_FREE?
> + * Pages being prepped should not have any flags set. It they are set,
> + * there has been a kernel bug or struct page corruption.
> */
> -#define PAGE_FLAGS_CHECK_AT_PREP (PAGE_FLAGS | \
> - 1 << PG_reserved | 1 << PG_dirty | 1 << PG_swapbacked)
> +#define PAGE_FLAGS_CHECK_AT_PREP ((1 << NR_PAGEFLAGS) - 1)
These are all the bits. Can we get rid of this definition?
> /*
> * For now, we report if PG_reserved was found set, but do not
> * clear it, and do not free the page. But we shall soon need
> * to do more, for when the ZERO_PAGE count wraps negative.
> */
> - return PageReserved(page);
> + if (PageReserved(page))
> + return 1;
> + if (page->flags & PAGE_FLAGS_CHECK_AT_PREP)
> + page->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
> + return 0;
The name PAGE_FLAGS_CHECK_AT_PREP is strange. We clear these flags without
message. This is equal to
page->flags &=~PAGE_FLAGS_CHECK_AT_PREP;
You can drop the if...
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-01 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 0:37 [PATCH 0/8] badpage: more resilient bad page pte and rmap Hugh Dickins
2008-12-01 0:40 ` [PATCH 1/8] badpage: simplify page_alloc flag check+clear Hugh Dickins
2008-12-01 14:47 ` Christoph Lameter [this message]
2008-12-01 23:50 ` Hugh Dickins
2008-12-02 2:21 ` Christoph Lameter
2008-12-02 10:39 ` Hugh Dickins
2008-12-02 13:12 ` Christoph Lameter
2008-12-02 14:12 ` Hugh Dickins
2008-12-03 0:57 ` Andrew Morton
2008-12-01 0:41 ` [PATCH 2/8] badpage: keep any bad page out of circulation Hugh Dickins
2008-12-01 14:49 ` Christoph Lameter
2008-12-01 23:19 ` Hugh Dickins
2008-12-01 0:42 ` [PATCH 3/8] badpage: replace page_remove_rmap Eeek and BUG Hugh Dickins
2008-12-01 0:43 ` [PATCH 4/8] badpage: vm_normal_page use print_bad_pte Hugh Dickins
2008-12-01 0:44 ` [PATCH 5/8] badpage: zap print_bad_pte on swap and file Hugh Dickins
2008-12-01 0:45 ` [PATCH 6/8] badpage: remove vma from page_remove_rmap Hugh Dickins
2008-12-01 0:46 ` [PATCH 7/8] badpage: ratelimit print_bad_pte and bad_page Hugh Dickins
2008-12-03 0:56 ` Andrew Morton
2008-12-03 13:04 ` Hugh Dickins
2008-12-01 0:48 ` [PATCH 8/8] badpage: KERN_ALERT BUG instead of KERN_EMERG Hugh Dickins
2008-12-01 14:40 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0812010843230.15331@quilx.com \
--to=cl@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rja@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox