From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Xiaotian Feng <xtfeng@gmail.com>,
linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at mm/vmscan.c:1114
Date: Tue, 2 Aug 2011 10:15:00 -0700 [thread overview]
Message-ID: <20110802101500.3f1d53c5.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110802142459.GF10436@suse.de>
On Tue, 2 Aug 2011 15:24:59 +0100 Mel Gorman <mgorman@suse.de> wrote:
> On Tue, Aug 02, 2011 at 03:09:57PM +0800, Xiaotian Feng wrote:
> > Hi,
> > __ __I'm hitting the kernel BUG at mm/vmscan.c:1114 twice, each time I
> > was trying to build my kernel. The photo of crash screen and my config
> > is attached. Thanks.
> > Regards
> > Xiaotian
>
> I am obviously blind because in 3.0, I cannot see what BUG is at
> mm/vmscan.c:1114 :(. I see
>
> 1109: /*
> 1110: * If we don't have enough swap space, reclaiming of
> 1111: * anon page which don't already have a swap slot is
> 1112: * pointless.
> 1113: */
> 1114: if (nr_swap_pages <= 0 && PageAnon(cursor_page) &&
> 1115: !PageSwapCache(cursor_page))
> 1116: break;
> 1117:
> 1118: if (__isolate_lru_page(cursor_page, mode, file) == 0) {
> 1119: list_move(&cursor_page->lru, dst);
> 1120: mem_cgroup_del_lru(cursor_page);
>
> Is this 3.0 vanilla or are there some other patches applied?
>
"3.0.0+": Current mainline.
static unsigned long isolate_lru_pages(unsigned long nr_to_scan,
struct list_head *src, struct list_head *dst,
unsigned long *scanned, int order, int mode, int file)
{
unsigned long nr_taken = 0;
unsigned long nr_lumpy_taken = 0;
unsigned long nr_lumpy_dirty = 0;
unsigned long nr_lumpy_failed = 0;
unsigned long scan;
for (scan = 0; scan < nr_to_scan && !list_empty(src); scan++) {
struct page *page;
unsigned long pfn;
unsigned long end_pfn;
unsigned long page_pfn;
int zone_id;
page = lru_to_page(src);
prefetchw_prev_lru_page(page, src, flags);
VM_BUG_ON(!PageLRU(page));
switch (__isolate_lru_page(page, mode, file)) {
case 0:
list_move(&page->lru, dst);
mem_cgroup_del_lru(page);
nr_taken += hpage_nr_pages(page);
break;
case -EBUSY:
/* else it is being freed elsewhere */
list_move(&page->lru, src);
mem_cgroup_rotate_lru_list(page, page_lru(page));
continue;
default:
-->> BUG();
}
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-02 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJn8CcE20-co4xNOD8c+0jMeABrc1mjmGzju3xT34QwHHHFsUA@mail.gmail.com>
[not found] ` <CAJn8CcG-pNbg88+HLB=tRr26_R+A0RxZEWsJQg4iGe4eY2noXA@mail.gmail.com>
2011-08-02 7:22 ` Andrew Morton
2011-08-03 6:44 ` Xiaotian Feng
2011-08-03 8:54 ` Mel Gorman
2011-08-03 9:02 ` Li Zefan
2011-08-04 3:54 ` Xiaotian Feng
2011-08-05 8:42 ` Xiaotian Feng
2011-08-05 9:19 ` Mel Gorman
2011-08-05 12:09 ` Xiaotian Feng
2011-08-05 12:30 ` Xiaotian Feng
2011-08-05 12:55 ` Mel Gorman
2011-08-05 15:51 ` Christoph Lameter
2011-08-02 14:24 ` Mel Gorman
2011-08-02 17:15 ` Andrew Morton [this message]
2011-08-03 6:45 ` Xiaotian Feng
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=20110802101500.3f1d53c5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=xtfeng@gmail.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