linux-kernel - Re: BUG: Bad rss-counter state mm:ffff8800c5a96000 idx:3 val:3894

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: <20151231093248.4ce475e2@canb.auug.org.au>
Date:	Thu, 31 Dec 2015 09:32:48 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Michal Hocko <mhocko@...nel.org>,
	Jeremiah Mahler <jmmahler@...il.com>,
	linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
	Andy Lutomirski <luto@...capital.net>,
	Will Drewry <wad@...omium.org>, Ingo Molnar <mingo@...nel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: BUG: Bad rss-counter state mm:ffff8800c5a96000 idx:3 val:3894

Hi Andrew,

On Tue, 29 Dec 2015 10:30:37 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 29 Dec 2015 17:23:47 +0100 Michal Hocko <mhocko@...nel.org> wrote:
> 
> > [CCing Andrew]
> > 
> > On Thu 24-12-15 09:12:53, Jeremiah Mahler wrote:  
> > > all,
> > > 
> > > I have started seeing a "Bad rss-counter" message in the logs with
> > > the latest linux-next 20151222+.
> > > 
> > >   [  458.282192] BUG: Bad rss-counter state mm:ffff8800c5a96000 idx:3 val:3894  
> > 
> > This is MM_SHMEMPAGES so an "unamapped" shmem memory. One possible
> > reason might be an unitialized zap_details used from unmap_mapping_range
> > during truncate introduced by "mm, oom: introduce oom reaper" from the
> > mmotm tree. There is a fix for this which is still pending
> > http://lkml.kernel.org/r/1450487091-7822-1-git-send-email-sasha.levin%40oracle.com  
> 
> That won't be getting fixed until linux-next returns from holidays.
> 
> This:
> 
> --- a/mm/memory.c~mm-oom-introduce-oom-reaper-fix-5-fix
> +++ a/mm/memory.c
> @@ -2415,7 +2415,7 @@ static inline void unmap_mapping_range_t
>  void unmap_mapping_range(struct address_space *mapping,
>  		loff_t const holebegin, loff_t const holelen, int even_cows)
>  {
> -	struct zap_details details;
> +	struct zap_details details = { };
>  	pgoff_t hba = holebegin >> PAGE_SHIFT;
>  	pgoff_t hlen = (holelen + PAGE_SIZE - 1) >> PAGE_SHIFT;
>  

OK, I have added the following from mmots to linux-next today (though I
may not get a release done):

mm-oom-introduce-oom-reaper-fix-4-fix.patch
mm-oom-introduce-oom-reaper-fix-4.patch
mm-oom-introduce-oom-reaper-fix-5-fix.patch
mm-oom-introduce-oom-reaper-fix-5.patch
mm-oom-introduce-oom-reaper-fix-6.patch
mmoom-exclude-tif_memdie-processes-from-candidates.patch

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
--
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/