All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	kosaki.motohiro@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, davej@redhat.com, mgorman@suse.de,
	cl@linux.com, stable@vger.kernel.org
Subject: Re: [PATCH 0/6][resend] mempolicy memory corruption fixlet
Date: Wed, 15 Aug 2012 13:20:50 -0700	[thread overview]
Message-ID: <20120815132050.12f4dec4.akpm@linux-foundation.org> (raw)
In-Reply-To: <CA+5PVA7YejzbWDEpX=gj8s2QAQtgoxyNUUa5HhGtVGY+2BHqRA@mail.gmail.com>

On Wed, 15 Aug 2012 07:40:46 -0400
Josh Boyer <jwboyer@gmail.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	kosaki.motohiro@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, davej@redhat.com, mgorman@suse.de,
	cl@linux.com, stable@vger.kernel.org
Subject: Re: [PATCH 0/6][resend] mempolicy memory corruption fixlet
Date: Wed, 15 Aug 2012 13:20:50 -0700	[thread overview]
Message-ID: <20120815132050.12f4dec4.akpm@linux-foundation.org> (raw)
In-Reply-To: <CA+5PVA7YejzbWDEpX=gj8s2QAQtgoxyNUUa5HhGtVGY+2BHqRA@mail.gmail.com>

On Wed, 15 Aug 2012 07:40:46 -0400
Josh Boyer <jwboyer@gmail.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.

  reply	other threads:[~2012-08-15 20:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  9:17 [PATCH 0/6][resend] mempolicy memory corruption fixlet kosaki.motohiro
2012-06-11  9:17 ` kosaki.motohiro
2012-06-11  9:17 ` [PATCH 1/6] Revert "mm: mempolicy: Let vma_merge and vma_split handle vma->vm_policy linkages" kosaki.motohiro
2012-06-11  9:17   ` kosaki.motohiro
2012-06-11 14:43   ` Christoph Lameter
2012-06-11 14:43     ` Christoph Lameter
2012-06-11  9:17 ` [PATCH 2/6] mempolicy: remove all mempolicy sharing kosaki.motohiro
2012-06-11  9:17   ` kosaki.motohiro
2012-06-11 15:02   ` Christoph Lameter
2012-06-11 15:02     ` Christoph Lameter
2012-06-12 16:46     ` KOSAKI Motohiro
2012-06-12 16:46       ` KOSAKI Motohiro
2012-06-12 16:46       ` KOSAKI Motohiro
2012-06-12 13:55   ` Mel Gorman
2012-06-12 13:55     ` Mel Gorman
2012-06-12 16:45     ` KOSAKI Motohiro
2012-06-12 16:45       ` KOSAKI Motohiro
2012-06-11  9:17 ` [PATCH 3/6] mempolicy: fix a race in shared_policy_replace() kosaki.motohiro
2012-06-11  9:17   ` kosaki.motohiro
2012-06-11  9:17 ` [PATCH 4/6] mempolicy: fix refcount leak in mpol_set_shared_policy() kosaki.motohiro
2012-06-11  9:17   ` kosaki.motohiro
2012-06-11  9:17 ` [PATCH 5/6] mempolicy: fix a memory corruption by refcount imbalance in alloc_pages_vma() kosaki.motohiro
2012-06-11  9:17   ` kosaki.motohiro
2012-06-11 13:33   ` Ben Hutchings
2012-06-11 15:24     ` KOSAKI Motohiro
2012-06-11 15:24       ` KOSAKI Motohiro
2012-06-12 14:20   ` Mel Gorman
2012-06-12 14:20     ` Mel Gorman
2012-06-12 16:31     ` KOSAKI Motohiro
2012-06-12 16:31       ` KOSAKI Motohiro
2012-06-11  9:17 ` [PATCH 6/6] MAINTAINERS: Added MEMPOLICY entry kosaki.motohiro
2012-06-11  9:17   ` kosaki.motohiro
2012-06-11 15:01 ` [PATCH 0/6][resend] mempolicy memory corruption fixlet Christoph Lameter
2012-06-11 15:01   ` Christoph Lameter
2012-07-31 12:33 ` Josh Boyer
2012-07-31 12:33   ` Josh Boyer
2012-08-06 19:32   ` KOSAKI Motohiro
2012-08-06 19:32     ` KOSAKI Motohiro
2012-08-15 11:40     ` Josh Boyer
2012-08-15 11:40       ` Josh Boyer
2012-08-15 20:20       ` Andrew Morton [this message]
2012-08-15 20:20         ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120815132050.12f4dec4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=davej@redhat.com \
    --cc=jwboyer@gmail.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.