linux-kernel - Re: kswapd craziness in 3.7

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: <20121204195008.GD24381@cmpxchg.org>
Date:	Tue, 4 Dec 2012 14:50:08 -0500
From:	Johannes Weiner <hannes@...xchg.org>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	Zdenek Kabelac <zkabelac@...hat.com>, Mel Gorman <mgorman@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rik van Riel <riel@...hat.com>,
	George Spelvin <linux@...izon.com>,
	Johannes Hirte <johannes.hirte@....tu-ilmenau.de>,
	Thorsten Leemhuis <fedora@...mhuis.info>,
	Tomas Racek <tracek@...hat.com>, Jan Kara <jack@...e.cz>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Josh Boyer <jwboyer@...il.com>, Valdis.Kletnieks@...edu,
	Bruno Wolff III <bruno@...ff.to>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: kswapd craziness in 3.7

On Tue, Dec 04, 2012 at 05:22:38PM +0100, Jiri Slaby wrote:
> On 12/04/2012 05:11 PM, Johannes Weiner wrote:
> >>>> Any chance you could retry with this patch on top?
> >>
> >> It does not apply to -next :/. Should I try anything else?
> > 
> > The COMPACTION_BUILD changed to IS_ENABLED(CONFIG_COMPACTION), below
> > is a -next patch.  I hope you don't run into other problems that come
> > out of -next craziness, because Linus is kinda waiting for this to be
> > resolved to release 3.8.  If you've always tested against -next so far
> > and it worked otherwise, don't change the environment now, please.  If
> > you just started, it would make more sense to test based on 3.7-rc8.
> 
> I reported the issue as soon as it appeared in -next for the first time
> on Oct 12. Since then I'm constantly hitting the issue (well, there were
> more than one I suppose, but not all of them were fixed by now) until
> now. I run only -next...

Okay.  Yes, it was a couple of problems, but not everybody hit the
same subset.

> Going to apply the patch now.

Thanks!
--
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/