From: Pravin Shelar <pshelar@nicira.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <cl@linux.com>,
penberg@kernel.org, aarcange@redhat.com, linux-mm@kvack.org,
abhide@nicira.com, Jesse Gross <jesse@nicira.com>
Subject: Re: [Resend PATCH v2] mm: Fix slab->page _count corruption.
Date: Mon, 11 Jun 2012 11:31:55 -0700 [thread overview]
Message-ID: <CALnjE+oS0JptkgEta-ysCLWzW-zEK7NB0rkg3DG-gYnB4MZzoA@mail.gmail.com> (raw)
In-Reply-To: <20120608141945.4df63d95.akpm@linux-foundation.org>
On Fri, Jun 8, 2012 at 2:19 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> 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?
>
We are working on zero copy io over skb in Open-vswitch. thats when we
so this panic when we tried to get_page() over skb linear data
allocated slub. But then I realized that it could potentially affect
other subsystems as well, e.g. xfs and ocfs, which does page struct
updates on slub objects.
--
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-11 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 19:20 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 [this message]
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=CALnjE+oS0JptkgEta-ysCLWzW-zEK7NB0rkg3DG-gYnB4MZzoA@mail.gmail.com \
--to=pshelar@nicira.com \
--cc=aarcange@redhat.com \
--cc=abhide@nicira.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=jesse@nicira.com \
--cc=linux-mm@kvack.org \
--cc=penberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox