From: "Jörn Engel" <joern@logfs.org>
To: Steve Capper <steve.capper@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Jul 3
Date: Wed, 3 Jul 2013 10:48:03 -0400 [thread overview]
Message-ID: <20130703144802.GA32130@logfs.org> (raw)
In-Reply-To: <20130703112539.GA32584@linaro.org>
On Wed, 3 July 2013 12:25:41 +0100, Steve Capper wrote:
>
> Today's linux-next appears to introduce some BUGs when running the libhugetlbfs
> testsuite (under both ARM64 and x86_64):
>
> [ 94.320661] BUG: Bad rss-counter state mm:ffff880119461040 idx:1 val:-512
> [ 94.330346] BUG: Bad rss-counter state mm:ffff880119460680 idx:1 val:-2560
> [ 94.341746] BUG: Bad rss-counter state mm:ffff880119460d00 idx:1 val:-512
> [ 94.347518] BUG: Bad rss-counter state mm:ffff880119460d00 idx:1 val:-512
> [ 94.415203] BUG: Bad rss-counter state mm:ffff8801194f9040 idx:1 val:-1024
>
> I've bisected this to commit:
> commit 446313e3e4e7274c4d1e449d107fab6c041ec59c
> hugetlb: properly account rss
>
> The bad counter values I get are all negative.
>
> To reproduce this, just run through the latest libhugetlbfs test suite, these
> warnings appear pretty much immediately. (I set aside 200 huge pages first):
> http://libhugetlbfs.sourceforge.net/
>
> Reverting this commit allows the test suite to run without problems.
Thank you, I will have a look. For the interim, dropping this patch
from -mm seems the best approach.
Jörn
--
Geld macht nicht glücklich.
Glück macht nicht satt.
next prev parent reply other threads:[~2013-07-03 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 8:06 linux-next: Tree for Jul 3 Stephen Rothwell
2013-07-03 8:06 ` Stephen Rothwell
2013-07-03 11:25 ` Steve Capper
2013-07-03 14:48 ` Jörn Engel [this message]
2013-07-08 4:39 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2014-07-03 5:53 Stephen Rothwell
2015-07-03 4:08 Stephen Rothwell
2017-07-03 9:03 Stephen Rothwell
2018-07-03 5:15 Stephen Rothwell
2019-07-03 11:49 Stephen Rothwell
2020-07-03 7:26 Stephen Rothwell
2023-07-03 2:20 Stephen Rothwell
2024-07-03 6:16 Stephen Rothwell
2025-07-03 9:37 Stephen Rothwell
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=20130703144802.GA32130@logfs.org \
--to=joern@logfs.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=steve.capper@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.