Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <739807cf-4551-4760-83e0-a94026b5c1b8@acm.org>
Date:   Tue, 4 Jul 2023 07:11:37 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Subject: Re: [linux-next:master] BUILD REGRESSION
 296d53d8f84ce50ffaee7d575487058c8d437335
Content-Language: en-US
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
References: <202307032309.v4K1IBoR-lkp@intel.com>
 <7d3d61c694c0e57b096ff7af6277ed6b@kernel.org>
From:   Bart Van Assche <bvanassche@acm.org>
In-Reply-To: <7d3d61c694c0e57b096ff7af6277ed6b@kernel.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

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.