From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <cl@linux.com>
Cc: Pravin B Shelar <pshelar@nicira.com>,
penberg@kernel.org, aarcange@redhat.com, linux-mm@kvack.org,
abhide@nicira.com
Subject: Re: [Resend PATCH v2] mm: Fix slab->page _count corruption.
Date: Fri, 8 Jun 2012 13:32:26 -0700 [thread overview]
Message-ID: <20120608133226.cd9a1167.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1206081514130.4213@router.home>
On Fri, 8 Jun 2012 15:15:50 -0500 (CDT)
Christoph Lameter <cl@linux.com> wrote:
> On Fri, 8 Jun 2012, Andrew Morton wrote:
>
> > OK. I assume this bug has been there for quite some time.
>
> Well the huge pages refcount tricks caused the issue.
>
> > How serious is it? Have people been reporting it in real workloads?
> > How to trigger it? IOW, does this need -stable backporting?
>
> Possibly.
that was all admirably indecisive.
> > Also, someone forgot to document these:
> >
> > struct {
> > unsigned inuse:16;
> > unsigned objects:15;
> > unsigned frozen:1;
> > };
>
> So far I thouight that the field names are pretty clear on their own.
Kidding? I had to grep the tree just to find out which subsystem owns
these.
--
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>
next prev parent reply other threads:[~2012-06-08 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 19:20 [Resend PATCH v2] mm: Fix slab->page _count corruption Pravin B Shelar
2012-06-08 20:10 ` Andrew Morton
2012-06-08 20:15 ` Christoph Lameter
2012-06-08 20:23 ` Pravin Shelar
2012-06-08 21:19 ` Andrew Morton
2012-06-11 18:31 ` Pravin Shelar
2012-06-08 20:32 ` Andrew Morton [this message]
2012-06-08 21:25 ` Christoph Lameter
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=20120608133226.cd9a1167.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=abhide@nicira.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=pshelar@nicira.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 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.