From: Paolo Bonzini <pbonzini@redhat.com>
To: kernel test robot <oliver.sang@intel.com>,
David Matlack <dmatlack@google.com>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, kvm@vger.kernel.org,
Ben Gardon <bgardon@google.com>, Joerg Roedel <joro@8bytes.org>,
Jim Mattson <jmattson@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Janis Schoetterl-Glausch <scgl@linux.vnet.ibm.com>,
Junaid Shahid <junaids@google.com>,
Oliver Upton <oupton@google.com>,
Harish Barathvajasankar <hbarath@google.com>,
Peter Xu <peterx@redhat.com>, Peter Shier <pshier@google.com>
Subject: Re: [KVM] d3750a0923: WARNING:possible_circular_locking_dependency_detected
Date: Mon, 6 Dec 2021 07:55:18 +0100 [thread overview]
Message-ID: <56b9d000-8743-52cb-4f10-4d3fa2b30f29@redhat.com> (raw)
In-Reply-To: <20211205133039.GD33002@xsang-OptiPlex-9020>
On 12/5/21 14:30, kernel test robot wrote:
>
> Chain exists of:
> fs_reclaim --> mmu_notifier_invalidate_range_start --> &(kvm)->mmu_lock
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(&(kvm)->mmu_lock);
> lock(mmu_notifier_invalidate_range_start);
> lock(&(kvm)->mmu_lock);
> lock(fs_reclaim);
>
David, this is yours; basically, kvm_mmu_topup_memory_cache must be
called outside the mmu_lock.
Paolo
next prev parent reply other threads:[~2021-12-06 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211119235759.1304274-14-dmatlack@google.com>
2021-12-05 13:30 ` kernel test robot
2021-12-06 6:55 ` Paolo Bonzini [this message]
2021-12-06 17:19 ` David Matlack
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=56b9d000-8743-52cb-4f10-4d3fa2b30f29@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=hbarath@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=junaids@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=oupton@google.com \
--cc=peterx@redhat.com \
--cc=pshier@google.com \
--cc=scgl@linux.vnet.ibm.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
all inboxes | Powered by JetHome®