linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Dave Hansen <dave@sr71.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Shaohua Li <shli@kernel.org>,
	Anton Vorontsov <anton.vorontsov@linaro.org>,
	Minchan Kim <minchan@kernel.org>
Subject: Re: mmotm-2013-05-22: Bad page state
Date: Wed, 29 May 2013 10:15:30 +0100	[thread overview]
Message-ID: <20130529091530.GA29426@suse.de> (raw)
In-Reply-To: <51A526D9.3020803@sr71.net>

On Tue, May 28, 2013 at 02:51:21PM -0700, Dave Hansen wrote:
> I was rebasing my mapping->radix_tree lock batching patches on top of
> Mel's stuff.  It looks like something is jumping the gun and freeing a
> page before it has been written out.  Somebody probably did an extra
> put_page() or something.
> 
> I'm running 3.10.0-rc2-mm1-00322-g8d4c612 from
> 
> 	git://git.cmpxchg.org/linux-mmotm.git
> 
> This is pretty reproducible.  I'll go try and test plain 3.10-rc2 next
> to make sure it's not coming from Linus's stuff.
> 

Patch 1 from the follow-up series "mm: vmscan: Block kswapd if it is
encountering pages under writeback -fix"

The rest of that follow-up series needs further work and I'm still
working on it but patch 1 is what fixes this particular problem.
Changelog says why.

-- 
Mel Gorman
SUSE Labs

--
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>

      parent reply	other threads:[~2013-05-29  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 21:51 mmotm-2013-05-22: Bad page state Dave Hansen
2013-05-28 21:53 ` Dave Hansen
2013-05-29  9:15 ` Mel Gorman [this message]

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=20130529091530.GA29426@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=anton.vorontsov@linaro.org \
    --cc=dave@sr71.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=shli@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).