Re: mm: kernel BUG at include/linux/swapops.h:131!

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Sasha Levin <sasha.levin@oracle.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	khlebnikov@openvz.org, LKML <linux-kernel@vger.kernel.org>,
	Wanpeng Li <liwanp@linux.vnet.ibm.com>,
	Bob Liu <bob.liu@oracle.com>
Subject: Re: mm: kernel BUG at include/linux/swapops.h:131!
Date: Mon, 23 Dec 2013 22:01:10 -0500	[thread overview]
Message-ID: <52B8F8F6.1080500@oracle.com> (raw)
In-Reply-To: <20131224025127.GA2835@lge.com>

On 12/23/2013 09:51 PM, Joonsoo Kim wrote:
> On Mon, Dec 23, 2013 at 12:24:02PM -0500, Sasha Levin wrote:
>> >Ping?
>> >
>> >I've also Cc'ed the "this page shouldn't be locked at all" team.
> Hello,
>
> I can't find the reason of this problem.
> If it is reproducible, how about bisecting?

While it reproduces under fuzzing it's pretty hard to bisect it with
the amount of issues uncovered by trinity recently.

I can add any debug code to the site of the BUG if that helps.


Thanks,
Sasha

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

WARNING: multiple messages have this Message-ID (diff)

From: Sasha Levin <sasha.levin@oracle.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	khlebnikov@openvz.org, LKML <linux-kernel@vger.kernel.org>,
	Wanpeng Li <liwanp@linux.vnet.ibm.com>,
	Bob Liu <bob.liu@oracle.com>
Subject: Re: mm: kernel BUG at include/linux/swapops.h:131!
Date: Mon, 23 Dec 2013 22:01:10 -0500	[thread overview]
Message-ID: <52B8F8F6.1080500@oracle.com> (raw)
In-Reply-To: <20131224025127.GA2835@lge.com>

On 12/23/2013 09:51 PM, Joonsoo Kim wrote:
> On Mon, Dec 23, 2013 at 12:24:02PM -0500, Sasha Levin wrote:
>> >Ping?
>> >
>> >I've also Cc'ed the "this page shouldn't be locked at all" team.
> Hello,
>
> I can't find the reason of this problem.
> If it is reproducible, how about bisecting?

While it reproduces under fuzzing it's pretty hard to bisect it with
the amount of issues uncovered by trinity recently.

I can add any debug code to the site of the BUG if that helps.


Thanks,
Sasha

next prev parent reply	other threads:[~2013-12-24  3:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 15:37 mm: kernel BUG at include/linux/swapops.h:131! Sasha Levin
2013-12-18 15:37 ` Sasha Levin
2013-12-18 15:41 ` Cyrill Gorcunov
2013-12-18 15:41   ` Cyrill Gorcunov
2013-12-18 15:46   ` Cyrill Gorcunov
2013-12-18 15:46     ` Cyrill Gorcunov
2013-12-23 17:24 ` Sasha Levin
2013-12-23 17:24   ` Sasha Levin
2013-12-24  2:51   ` Joonsoo Kim
2013-12-24  2:51     ` Joonsoo Kim
2013-12-24  3:01     ` Sasha Levin [this message]
2013-12-24  3:01       ` Sasha Levin
2013-12-24  6:07       ` Joonsoo Kim
2013-12-24  6:07         ` Joonsoo Kim
2013-12-24  7:45         ` Joonsoo Kim
2013-12-24  7:45           ` Joonsoo Kim
2013-12-25  1:07           ` Wanpeng Li
2013-12-26  1:21           ` Bob Liu
2013-12-26  1:21             ` Bob Liu
2013-12-26  5:51             ` Konstantin Khlebnikov
2013-12-26  6:18             ` Konstantin Khlebnikov
2013-12-26  6:18               ` Konstantin Khlebnikov
2013-12-26  6:27               ` Wanpeng Li
2013-12-24 19:27         ` Sasha Levin
2013-12-24 19:27           ` Sasha Levin
2014-01-02  6:36   ` Bob Liu
2014-01-02  6:36     ` Bob Liu
2014-01-04  2:57     ` Sasha Levin
2014-01-04  2:57       ` 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=52B8F8F6.1080500@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bob.liu@oracle.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liwanp@linux.vnet.ibm.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.