From: Marc Zyngier <maz@misterjones.org>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
dri-devel@lists.freedesktop.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-cifs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org,
samba-technical@lists.samba.org
Subject: Re: [linux-next:master] BUILD REGRESSION 8c33787278ca8db73ad7d23f932c8c39b9f6e543
Date: Tue, 30 May 2023 22:32:22 +0100 [thread overview]
Message-ID: <d65700431ed60877d3ec8e88e1211a97@misterjones.org> (raw)
In-Reply-To: <20230530182123.UilBt%lkp@intel.com>
On 2023-05-30 19:21, kernel test robot wrote:
> tree/branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> branch HEAD: 8c33787278ca8db73ad7d23f932c8c39b9f6e543 Add linux-next
> specific files for 20230530
>
> Error/Warning reports:
>
> https://lore.kernel.org/oe-kbuild-all/202305070840.X0G3ofjl-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> include/drm/drm_print.h:456:39: error: format '%ld' expects argument
> of type 'long int', but argument 4 has type 'size_t' {aka 'unsigned
> int'} [-Werror=format=]
>
> 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 warning looks wrong. The "issue" seems that we acquire the lock
before exiting the function, but the the whole point is that the
lock is supposed to be held all along (it is dropped and then acquired
again).
I guess the coccinelle checker doesn't spot this construct?
M.
--
Who you jivin' with that Cosmik Debris?
prev parent reply other threads:[~2023-05-30 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 18:21 kernel test robot
2023-05-30 21:32 ` Marc Zyngier [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=d65700431ed60877d3ec8e88e1211a97@misterjones.org \
--to=maz@misterjones.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=samba-technical@lists.samba.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