From: Bart Van Assche <bvanassche@acm.org>
To: Marc Zyngier <maz@kernel.org>, kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kunit-dev@googlegroups.com, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [linux-next:master] BUILD REGRESSION 296d53d8f84ce50ffaee7d575487058c8d437335
Date: Tue, 4 Jul 2023 07:11:37 -0700 [thread overview]
Message-ID: <739807cf-4551-4760-83e0-a94026b5c1b8@acm.org> (raw)
In-Reply-To: <7d3d61c694c0e57b096ff7af6277ed6b@kernel.org>
On 7/4/23 00:15, Marc Zyngier wrote:
> On 2023-07-03 16:11, kernel test robot wrote:
>> tree/branch:
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> master
>> branch HEAD: 296d53d8f84ce50ffaee7d575487058c8d437335 Add linux-next
>> specific files for 20230703
>>
>
> [...]
>
>> Unverified Error/Warning (likely false positive, please contact us if
>> interested):
>>
>> arch/arm64/kvm/mmu.c:147:3-9: preceding lock on line 140
>
> This *is* a false positive. The function is entered with a lock
> held, it will exit with the lock held as well. Inside the body
> of the function, we release and reacquire the lock.
Which tool reported this message? If this message was reported by
sparse, has it been considered to add a __must_hold() annotation?
Thanks,
Bart.
next prev parent reply other threads:[~2023-07-04 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:11 kernel test robot
2023-07-04 7:15 ` Marc Zyngier
2023-07-04 14:11 ` Bart Van Assche [this message]
2023-07-10 5:51 ` Yujie Liu
2023-07-04 10:30 ` Shay Drory
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=739807cf-4551-4760-83e0-a94026b5c1b8@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maz@kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox