mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Eric Sesterhenn <snakebyte@gmx.de>,
	linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
	James Morris <jmorris@namei.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: Redzone overwritten with CONFIG_SECURITY
Date: Tue, 27 May 2008 11:04:48 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805271104100.18436@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <84144f020805271059k11498424w3435b748f5254e2e@mail.gmail.com>

On Tue, 27 May 2008, Pekka Enberg wrote:

> Then it's likely that we corrupt hugetlbfs_inode_cachep because of
> SLUB merging and the real problem is somewhere else. Can you also try
> passing 'slub_nomerge" as a kernel parameter with SLUB?

Enabling Redzone disables merging. So its unrelated to merging.
 

  reply	other threads:[~2008-05-27 18:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 14:34 Eric Sesterhenn
2008-05-27 14:00 ` Eric Sesterhenn
2008-05-27 14:23   ` Vegard Nossum
2008-05-27 14:53     ` Eric Sesterhenn
2008-05-27 14:55   ` Pekka Enberg
2008-05-27 15:00 ` Pekka Enberg
2008-05-27 15:11   ` Eric Sesterhenn
2008-05-27 16:11     ` Eric Sesterhenn
2008-05-27 17:59       ` Pekka Enberg
2008-05-27 18:04         ` Christoph Lameter [this message]
2008-05-27 17:47   ` Chris Wright
2008-05-28 10:03     ` Eric Sesterhenn
2008-05-28 21:51       ` Chris Wright
2008-05-31 23:24         ` Chris Wright
2008-05-27 18:25 ` Pekka Enberg

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=Pine.LNX.4.64.0805271104100.18436@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@sous-sol.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=snakebyte@gmx.de \
    --cc=vegard.nossum@gmail.com \
    --cc=wli@holomorphy.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

all inboxes | Powered by JetHome®