All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	LKML <linux-kernel@vger.kernel.org>,
	Xishi Qiu <qiuxishi@huawei.com>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: A oops occur when it calls kmem_cache_alloc
Date: Fri, 4 Mar 2016 20:22:29 +0800	[thread overview]
Message-ID: <56D97E05.2080106@huawei.com> (raw)
In-Reply-To: <56D96734.6050108@I-love.SAKURA.ne.jp>

On 2016/3/4 18:45, Tetsuo Handa wrote:
> On 2016/03/04 17:36, zhong jiang wrote:
>> The vmcore file show the collapse reason that the page had been removed
>> when we acqure the page and  prepare to remove the page from the slub
>>  partial list.
>>
>> The list is protected by the spin_lock from concurrent operation. And I find
>> that other core is wating the lock to alloc memory.  Therefore , The concurrent
>> access should be impossible.
>>
>> what situatios can happen ?  or it is a kernel bug potentially.  This question
>> almost impossible to produce again. The following is the call statck belonging to
>> the module.
> No kernel version, no clue.
>
>
>
   Sorry,  The kernel version is 3.4 stable version.  And The mainline , by comparison,  have no relative
   modification.

Thanks
zhongjiang

--
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: zhong jiang <zhongjiang@huawei.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	LKML <linux-kernel@vger.kernel.org>,
	Xishi Qiu <qiuxishi@huawei.com>,
	"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: A oops occur when it calls kmem_cache_alloc
Date: Fri, 4 Mar 2016 20:22:29 +0800	[thread overview]
Message-ID: <56D97E05.2080106@huawei.com> (raw)
In-Reply-To: <56D96734.6050108@I-love.SAKURA.ne.jp>

On 2016/3/4 18:45, Tetsuo Handa wrote:
> On 2016/03/04 17:36, zhong jiang wrote:
>> The vmcore file show the collapse reason that the page had been removed
>> when we acqure the page and  prepare to remove the page from the slub
>>  partial list.
>>
>> The list is protected by the spin_lock from concurrent operation. And I find
>> that other core is wating the lock to alloc memory.  Therefore , The concurrent
>> access should be impossible.
>>
>> what situatios can happen ?  or it is a kernel bug potentially.  This question
>> almost impossible to produce again. The following is the call statck belonging to
>> the module.
> No kernel version, no clue.
>
>
>
   Sorry,  The kernel version is 3.4 stable version.  And The mainline , by comparison,  have no relative
   modification.

Thanks
zhongjiang

  parent reply	other threads:[~2016-03-04 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  8:36 A oops occur when it calls kmem_cache_alloc zhong jiang
2016-03-04  8:36 ` zhong jiang
     [not found] ` <56D96734.6050108@I-love.SAKURA.ne.jp>
2016-03-04 12:22   ` zhong jiang [this message]
2016-03-04 12:22     ` zhong jiang

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=56D97E05.2080106@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=qiuxishi@huawei.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.