[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+5PVA7YejzbWDEpX=gj8s2QAQtgoxyNUUa5HhGtVGY+2BHqRA@mail.gmail.com>
Date: Wed, 15 Aug 2012 07:40:46 -0400
From: Josh Boyer <jwboyer@...il.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.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
Subject: Re: [PATCH 0/6][resend] mempolicy memory corruption fixlet
On Mon, Aug 6, 2012 at 3:32 PM, KOSAKI Motohiro
<kosaki.motohiro@...fujitsu.com> wrote:
> 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.
The series still isn't queued anywhere. Are you planning on resending
it again, or should it get picked up in a particular tree?
josh
--
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