linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	mgorman@suse.de
Subject: Re: [PATCH 0/5] mm: poison critical mm/ structs
Date: Thu, 2 Oct 2014 11:13:02 -0400	[thread overview]
Message-ID: <20141002151302.GA15348@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1410020154500.6444@eggly.anvils>

On Thu, Oct 02, 2014 at 02:23:08AM -0700, Hugh Dickins wrote:

 > I think these patches are fine for investigating whatever is the
 > problem currently afflicting you and mm under trinity; but we all
 > have our temporary debugging patches, I don't think all deserve
 > preservation in everyone else's kernel, that amounts to far more
 > clutter than any are worth.

One problem with keeping things like this in -mm (or other non-Linus tree)
is that they bit-rot quickly, and become a pain to apply, especially if
they are perpetually on top of other changes in -mm.

I looked at trying these patches on Linus' tree when Sasha posted them,
but lost motivation when I realized they needed other bits of -mm too.

It may be that after Andrews 3.18+ mega-merge things would be simpler,
but I have a feeling it wouldn't be long before the situation would
arise again.

	Dave

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

  parent reply	other threads:[~2014-10-02 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30  1:47 [PATCH 0/5] mm: poison critical mm/ structs Sasha Levin
2014-09-30  1:47 ` [PATCH 1/5] mm: add poisoning basics Sasha Levin
2014-09-30  1:47 ` [PATCH 2/5] mm: constify dump_page and friends Sasha Levin
2014-09-30  1:47 ` [PATCH 3/5] mm: poison mm_struct Sasha Levin
2014-09-30  1:47 ` [PATCH 4/5] mm: poison vm_area_struct Sasha Levin
2014-09-30  1:47 ` [PATCH 5/5] mm: poison page struct Sasha Levin
2014-10-07 22:02   ` Dave Hansen
2014-10-08  7:10     ` Christoph Lameter
2014-10-08 14:22     ` Sasha Levin
2014-10-01 21:07 ` [PATCH 0/5] mm: poison critical mm/ structs Andrew Morton
2014-10-01 21:39   ` Sasha Levin
2014-10-01 21:48     ` Andrew Morton
2014-10-02  3:51       ` Sasha Levin
2014-10-02  9:23     ` Hugh Dickins
2014-10-02 14:58       ` Sasha Levin
2014-10-07 22:16         ` Dave Hansen
2014-10-08 16:43           ` Sasha Levin
2014-10-02 15:13       ` Dave Jones [this message]
2014-10-09 19:11       ` Sasha Levin

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=20141002151302.GA15348@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=sasha.levin@oracle.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).