From: Andrew Morton <akpm@linux-foundation.org>
To: Pravin Shelar <pshelar@nicira.com>
Cc: Christoph Lameter <cl@linux.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 14:19:45 -0700 [thread overview]
Message-ID: <20120608141945.4df63d95.akpm@linux-foundation.org> (raw)
In-Reply-To: <CALnjE+rdvdj=XXd7iCYzL_BUGYsLQTM1mYRay+0q2iFxqiDqSw@mail.gmail.com>
On Fri, 8 Jun 2012 13:23:56 -0700
Pravin Shelar <pshelar@nicira.com> wrote:
> On Fri, Jun 8, 2012 at 1:15 PM, 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.
>
> If this patch is getting back-ported then we shld also do same for
> 5bf5f03c271907978 (mm: fix slab->page flags corruption) which fixes
> other issue related to slub and huge page sharing.
Well I don't know if either are getting backported yet.
To decide that we would have to understand the end-user impact of the
bug(s). Please tell us?
--
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 21:19 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 [this message]
2012-06-11 18:31 ` Pravin Shelar
2012-06-08 20:32 ` Andrew Morton
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=20120608141945.4df63d95.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.