From: Oliver Sang <oliver.sang@intel.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Zi Yan <ziy@nvidia.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Michal Hocko <mhocko@kernel.org>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com
Subject: Re: [mm/page_alloc] 44042b4498: WARNING:possible_recursive_locking_detected
Date: Wed, 28 Jul 2021 13:14:21 +0800 [thread overview]
Message-ID: <20210728051420.GA8616@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20210727143538.GB3809@techsingularity.net>
hi Mel Gorman,
On Tue, Jul 27, 2021 at 03:35:38PM +0100, Mel Gorman wrote:
> On Tue, Jul 27, 2021 at 10:31:36PM +0800, kernel test robot wrote:
> >
> >
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
> >
> > commit: 44042b4498728f4376e84bae1ac8016d146d850b ("mm/page_alloc: allow high-order pages to be stored on the per-cpu lists")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> >
>
> Does this warning happen after 187ad460b841 ("mm/page_alloc: avoid page
> allocator recursion with pagesets.lock held")? I ask because I see the
> stack_depot_save in the warning.
from our tests, this warning cannot be reproduced upon 187ad460b841.
Thanks for information!
>
> --
> Mel Gorman
> SUSE Labs
prev parent reply other threads:[~2021-07-28 4:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 14:31 [mm/page_alloc] 44042b4498: WARNING:possible_recursive_locking_detected kernel test robot
2021-07-27 14:35 ` Mel Gorman
2021-07-28 5:14 ` Oliver Sang [this message]
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=20210728051420.GA8616@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).