linux-kernel - Re: [PATCH 0/6][resend] mempolicy memory corruption fixlet

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]

Date:	Wed, 15 Aug 2012 13:20:50 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Josh Boyer <jwboyer@...il.com>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	kosaki.motohiro@...il.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, davej@...hat.com, mgorman@...e.de,
	cl@...ux.com, stable@...r.kernel.org
Subject: Re: [PATCH 0/6][resend] mempolicy memory corruption fixlet

On Wed, 15 Aug 2012 07:40:46 -0400
Josh Boyer <jwboyer@...il.com> wrote:

> >> I don't see these patches queued anywhere.  They aren't in linux-next,
> >> mmotm, or Linus' tree.  Did these get dropped?  Is the revert still
> >> needed?
> >
> > Sorry. my fault. yes, it is needed. currently, Some LTP was fail since
> > Mel's "mm: mempolicy: Let vma_merge and vma_split handle vma->vm_policy linkages" patch.
> 
> The series still isn't queued anywhere.  Are you planning on resending
> it again, or should it get picked up in a particular tree?

The patches need a refresh and a retest please, including incorporation
of Christoph's changelog modifications.

And for gawd's sake, please stop using my google address!  It messes me
all up.
--
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/