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]
Date:	Mon, 06 Aug 2012 15:32:05 -0400
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	jwboyer@...il.com
CC:	kosaki.motohiro@...il.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, akpm@...gle.com, davej@...hat.com,
	mgorman@...e.de, cl@...ux.com, stable@...r.kernel.org,
	kosaki.motohiro@...fujitsu.com
Subject: Re: [PATCH 0/6][resend] mempolicy memory corruption fixlet

On 7/31/2012 8:33 AM, Josh Boyer wrote:
> On Mon, Jun 11, 2012 at 5:17 AM,  <kosaki.motohiro@...il.com> wrote:
>> From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
>>
>> Hi
>>
>> This is trivial fixes of mempolicy meory corruption issues. There
>> are independent patches each ather. and, they don't change userland
>> ABIs.
>>
>> Thanks.
>>
>> changes from v1: fix some typo of changelogs s.
>>
>> -----------------------------------------------
>> KOSAKI Motohiro (6):
>>   Revert "mm: mempolicy: Let vma_merge and vma_split handle
>>     vma->vm_policy linkages"
>>   mempolicy: Kill all mempolicy sharing
>>   mempolicy: fix a race in shared_policy_replace()
>>   mempolicy: fix refcount leak in mpol_set_shared_policy()
>>   mempolicy: fix a memory corruption by refcount imbalance in
>>     alloc_pages_vma()
>>   MAINTAINERS: Added MEMPOLICY entry
>>
>>  MAINTAINERS    |    7 +++
>>  mm/mempolicy.c |  151 ++++++++++++++++++++++++++++++++++++++++----------------
>>  mm/shmem.c     |    9 ++--
>>  3 files changed, 120 insertions(+), 47 deletions(-)
> 
> 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.




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