All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oliver Glitta <glittao@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Vlastimil Babka <vbabka@suse.cz>,
	David Rientjes <rientjes@google.com>,
	Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	lkp@lists.01.org, lkp@intel.com
Subject: Re: [mm/slub]  ad36bafb3b: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c
Date: Wed, 9 Jun 2021 16:59:38 +0800	[thread overview]
Message-ID: <20210609085938.GD15555@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20210518170700.0ffdcaeb55cf64607120d5be@linux-foundation.org>

hi Andrew,

On Tue, May 18, 2021 at 05:07:00PM -0700, Andrew Morton wrote:
> On Sun, 16 May 2021 22:41:52 +0800 kernel test robot <oliver.sang@intel.com> wrote:
> 
> > FYI, we noticed the following commit (built with gcc-9):
> > 
> > commit: ad36bafb3bcdfdb98ae3516285bbb3ecd51d1597 ("mm/slub: use stackdepot to save stack trace in objects")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> > 
> 
> I expect
> https://lkml.kernel.org/r/20210516195150.26740-1-vbabka@suse.cz will
> fix this?
> 

we tested the patch, and it can fix the issue. thanks

WARNING: multiple messages have this Message-ID (diff)
From: Oliver Sang <oliver.sang@intel.com>
To: lkp@lists.01.org
Subject: Re: [mm/slub] ad36bafb3b: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c
Date: Wed, 09 Jun 2021 16:59:38 +0800	[thread overview]
Message-ID: <20210609085938.GD15555@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20210518170700.0ffdcaeb55cf64607120d5be@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

hi Andrew,

On Tue, May 18, 2021 at 05:07:00PM -0700, Andrew Morton wrote:
> On Sun, 16 May 2021 22:41:52 +0800 kernel test robot <oliver.sang@intel.com> wrote:
> 
> > FYI, we noticed the following commit (built with gcc-9):
> > 
> > commit: ad36bafb3bcdfdb98ae3516285bbb3ecd51d1597 ("mm/slub: use stackdepot to save stack trace in objects")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> > 
> 
> I expect
> https://lkml.kernel.org/r/20210516195150.26740-1-vbabka(a)suse.cz will
> fix this?
> 

we tested the patch, and it can fix the issue. thanks

  parent reply	other threads:[~2021-06-09  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 14:41 [mm/slub] ad36bafb3b: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c kernel test robot
2021-05-16 14:41 ` kernel test robot
2021-05-19  0:07 ` Andrew Morton
2021-05-19  0:07   ` Andrew Morton
2021-05-24  5:25   ` David Rientjes
2021-05-24  5:25     ` David Rientjes
2021-06-09  8:59   ` Oliver Sang [this message]
2021-06-09  8:59     ` Oliver Sang

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=20210609085938.GD15555@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=glittao@gmail.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vbabka@suse.cz \
    /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.