From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Chris Pearson <pearson.christopher.j@gmail.com>,
linux-mm@kvack.org, Andrea Arcangeli <aarcange@redhat.com>,
stable <stable@kernel.org>
Subject: Re: NULL poniter dereference in isolate_lru_pages 2.6.39.1
Date: Mon, 18 Jul 2011 16:18:19 -0700 [thread overview]
Message-ID: <20110718161819.506fe97c.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAEwNFnDwjWDF7Z4AUZg9rAHN6=n9nZ5tZe5U8USn7TpVCNsM6A@mail.gmail.com>
On Tue, 19 Jul 2011 07:48:11 +0900 Minchan Kim <minchan.kim@gmail.com> wrote:
> Thanks for the test, Chris.
> Andrew.
> We should push this into -stable.
That's
commit d179e84ba5da1d0024087d1759a2938817a00f3f
Author: Andrea Arcangeli <aarcange@redhat.com>
AuthorDate: Wed Jun 15 15:08:51 2011 -0700
Commit: Linus Torvalds <torvalds@linux-foundation.org>
CommitDate: Wed Jun 15 20:04:02 2011 -0700
mm: vmscan: do not use page_count without a page pin
>
> On Fri, Jul 15, 2011 at 10:48 AM, Chris Pearson
> <pearson.christopher.j@gmail.com> wrote:
> > That definately fixed it. __MTBF was about 20 days on those systems, since that patch we've had 200 server days with no problems.
> >
> > Thanks!
> >
> > On Tue, 12 Jul 2011, Minchan Kim wrote:
> >
> >>Date: Tue, 12 Jul 2011 09:16:09 +0900
> >>From: Minchan Kim <minchan.kim@gmail.com>
> >>To: Chris Pearson <pearson.christopher.j@gmail.com>
> >>Cc: linux-mm@kvack.org, Andrea Arcangeli <aarcange@redhat.com>,
> >> __ __Andrew Morton <akpm@linux-foundation.org>, stable <stable@kernel.org>
> >>Subject: Re: NULL poniter dereference in isolate_lru_pages 2.6.39.1
> >>
> >>On Tue, Jul 12, 2011 at 5:52 AM, Chris Pearson
> >><pearson.christopher.j@gmail.com> wrote:
> >>> We applied the patch to many servers. __No problems so far.
> >>>
> >>> The .config is attached.
> >>
> >>Thanks. I verified. The point where isolate_lru_pages + 0x225 is
> >>page_count exactly. So Andrea patch solves this problem apparently.
> >>Couldn't we throw this patch to stable tree?
> >>
> >>https://patchwork.kernel.org/patch/857442/
> >>
> >>>
> >>> What's the config option to get that debugging info in the future?
> >>
> >>CONFIG_DEBUG_INFO helps you. :)
> >>
> >>--
> >>Kind regards,
> >>Minchan Kim
> >>
> >
>
>
>
> --
> Kind regards,
> Minchan Kim
--
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-07-18 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 15:53 NULL poniter dereference in isolate_lru_pages 2.6.39.1 Chris Pearson
2011-07-08 5:14 ` Minchan Kim
2011-07-08 15:39 ` Chris Pearson
2011-07-10 23:05 ` Minchan Kim
2011-07-11 20:52 ` Chris Pearson
2011-07-12 0:16 ` Minchan Kim
2011-07-15 1:48 ` Chris Pearson
2011-07-18 22:48 ` Minchan Kim
2011-07-18 23:18 ` Andrew Morton [this message]
2011-07-18 23:32 ` Minchan Kim
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=20110718161819.506fe97c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=pearson.christopher.j@gmail.com \
--cc=stable@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).