All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: lkp@lists.01.org
Subject: Re: [mm/page_alloc] dbbee9d5cd: WARNING:possible_circular_locking_dependency_detected
Date: Tue, 13 Jul 2021 15:59:41 +0100	[thread overview]
Message-ID: <20210713145941.GG3809@techsingularity.net> (raw)
In-Reply-To: <20210713144057.GB28943@xsang-OptiPlex-9020>

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

On Tue, Jul 13, 2021 at 10:40:57PM +0800, kernel test robot wrote:
> 
> 
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):
> 
> commit: dbbee9d5cd83f9d0a29639e260516907ceb2ac3d ("mm/page_alloc: convert per-cpu list protection to local_lock")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 

Thanks, this will ultimately be fixed by https://lore.kernel.org/r/20210713135625.7615-1-mgorman(a)techsingularity.net

-- 
Mel Gorman
SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@techsingularity.net>
To: kernel test robot <oliver.sang@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Peter Zijlstra <peterz@infradead.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Ingo Molnar <mingo@kernel.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Michal Hocko <mhocko@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com
Subject: Re: [mm/page_alloc]  dbbee9d5cd: WARNING:possible_circular_locking_dependency_detected
Date: Tue, 13 Jul 2021 15:59:41 +0100	[thread overview]
Message-ID: <20210713145941.GG3809@techsingularity.net> (raw)
In-Reply-To: <20210713144057.GB28943@xsang-OptiPlex-9020>

On Tue, Jul 13, 2021 at 10:40:57PM +0800, kernel test robot wrote:
> 
> 
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):
> 
> commit: dbbee9d5cd83f9d0a29639e260516907ceb2ac3d ("mm/page_alloc: convert per-cpu list protection to local_lock")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 

Thanks, this will ultimately be fixed by https://lore.kernel.org/r/20210713135625.7615-1-mgorman@techsingularity.net

-- 
Mel Gorman
SUSE Labs

  reply	other threads:[~2021-07-13 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 14:40 [mm/page_alloc] dbbee9d5cd: WARNING:possible_circular_locking_dependency_detected kernel test robot
2021-07-13 14:40 ` kernel test robot
2021-07-13 14:59 ` Mel Gorman [this message]
2021-07-13 14:59   ` Mel Gorman

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=20210713145941.GG3809@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=lkp@lists.01.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 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.