linux-kernel - Re: exit_mmap() BUG_ON triggering since 3.1

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] [day] [month] [year] [list]

Message-Id: <20120305120749.b843fbde.akpm@linux-foundation.org>
Date:	Mon, 5 Mar 2012 12:07:49 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Hugh Dickins <hughd@...gle.com>,
	Andrea Arcangeli <aarcange@...hat.com>,
	Dave Jones <davej@...hat.com>,
	David Rientjes <rientjes@...gle.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	kernel-team@...oraproject.org
Subject: Re: exit_mmap() BUG_ON triggering since 3.1

On Mon, 5 Mar 2012 14:59:53 -0500
Josh Boyer <jwboyer@...hat.com> wrote:

> On Fri, Mar 02, 2012 at 03:09:29PM -0800, Hugh Dickins wrote:
> > On Fri, 2 Mar 2012, Andrew Morton wrote:
> > > On Fri, 2 Mar 2012 14:53:32 -0800 (PST)
> > > Hugh Dickins <hughd@...gle.com> wrote:
> > > 
> > > > Subject: Re: exit_mmap() BUG_ON triggering since 3.1
> > > > ...
> > > > Subject: [PATCH] mm: thp: fix BUG on mm->nr_ptes
> > > 
> > > So it's needed in 3.1.x and 3.2.x?
> > 
> > Indeed it would be needed in -stable, thanks, I forgot to add that.
> > 
> > And although Fedora only got reports from 3.1 onwards, I believe it
> > would equally be needed in 3.0.x.  3.1.x is closed down now, but
> > 3.0.x and 3.2.x are still open.
> > 
> > I've not yet tried applying it to the latest of either of those: maybe
> > it applies cleanly and correctly, but I could imagine movements too.
> > But the first step, yes, is to Cc: stable@...r.kernel.org
> 
> I don't see this in linux-next, 3.3-rcX, the stable-queue, or really
> anywhere at all at the moment.  Did the patch get swallowed up by some
> kind of evil code Eagle of Doom before making it into the safety of a
> tree somewhere?

I have it queued for 3.3.  It's taking a while to get things into -next
at present because they're breaking things faster than I can fix them :(

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