linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Capper <steve.capper@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Joern Engel <joern@logfs.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 3
Date: Wed, 3 Jul 2013 12:25:41 +0100	[thread overview]
Message-ID: <20130703112539.GA32584@linaro.org> (raw)
In-Reply-To: <20130703180620.6919bf7d7f13f7ed21046c68@canb.auug.org.au>

On Wed, Jul 03, 2013 at 06:06:20PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20130702:
> 
> The powerpc tree lost its build failure.
> 
> The device-mapper tree gained a conflict against the md tree.
> 
> The net-next tree gained a build failure for which I cherry-picked an
> upcoming fix.
> 
> The trivial tree gained conflicts against the btrfs and Linus' trees.
> 
> The xen-two tree gained a conflict against the tip tree.
> 
> The akpm tree lost some patches that turned up elsewhere.
> 
> The cpuinit tree lost a patch that turned up elsewhere.
> 
> ----------------------------------------------------------------------------
> 

Hi,
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.

Cheers,
-- 
Steve

  reply	other threads:[~2013-07-03 11:25 UTC|newest]

Thread overview: 11+ 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 11:25 ` Steve Capper [this message]
2013-07-03 14:48   ` Jörn Engel
2013-07-08  4:39     ` Stephen Rothwell
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

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=20130703112539.GA32584@linaro.org \
    --to=steve.capper@linaro.org \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).