lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FD12926.8050200@wwwdotorg.org>
Date:	Thu, 07 Jun 2012 16:20:22 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Konstantin Khlebnikov <khlebnikov@...nvz.org>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: linux-next: boot problem with next-20120607

On 06/07/2012 04:05 PM, Andrew Morton wrote:
> On Thu, 7 Jun 2012 13:53:20 +1000
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
>> Hi Andrew,
>>
>> My boot of next-20120607 in PowerPC produces lots of these warnings:
>>
>> BUG: Bad rss-counter state mm:c000000278508000 idx:0 val:-27
>> BUG: Bad rss-counter state mm:c000000278284000 idx:0 val:-27
>> BUG: Bad rss-counter state mm:c000000279e13000 idx:0 val:-27
>> BUG: Bad rss-counter state mm:c000000278285400 idx:0 val:-27
>>
>> And so on (with different mm, idx and val numbers).  Searching showed me
>> commit "mm: correctly synchronize rss-counters at exit/exec" which seems
>> to be there to fix this exact problem?
> 
> Well that's a worry.  Are you really sure
> mm-correctly-synchronize-rss-counters-at-exit-exec.patch was applied at
> the time?
> 
> There's been an extended amount of inconclusive waffling on that patch,
> but I thought it concerned the best way to fix it, rather than
> *whether* it fixes it.

I see those same errors on my ARM system. I found that reverting that
patch (105d42c mm: correctly synchronize rss-counters at exit/exec) made
them go away, although I didn't investigate whether that just removed
some debug print or actually solved a problem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ