From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 03F69280A56 for ; Wed, 26 Aug 2026 07:42:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787730175; cv=none; b=fG3MMEogoxN/unnDxy9tQBvzVfwzInWe3MFZskUTl5P6oM82P2Ig8DcHL8Y8QXAl0evpfNzrlTq9RiD8JJhcoDS/M5CMwO7EJhvWqjmbxjROjQn3Yv3bZi7oI6fSHW6F+IPXS7FsoOgZL68dFTuEDpxupWskxKgqcHOpByIUbFk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787730175; c=relaxed/simple; bh=vBJyn3WCv+xXfDa3D+lRtyk/Alm5dCZrQv2vmieraww=; h=Date:Message-ID:From:To:Cc:Subject:In-Reply-To:References: MIME-Version:Content-Type; b=B8uTvbtRWxVLlE9XTvU8pWUPzhVcsVrwKI1GgtPuMrYuUwaPyotOsi92FG/nESzB601hlNOWD7I6zBanWH+mW/rNJbeSJtDYdzQYXsaP/S6h1DkLH2F9k38FaWNKs+1VnFMOD2ebzExfeolhKZ5fhOjoSYxSgApzB1TqiNpK8Vw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=K++vII0g; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="K++vII0g" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA06B1F000E9; Wed, 26 Aug 2026 07:42:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787730173; bh=v/zTTEPBZyHdIeerYePVZm+2uNjDd1w6Yo9NtOjDfcc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=K++vII0gkvF0Wr5bBMtE12noEALqtZV9BwzTWLj+s2cR5eHnuY3a9Z02r7Yy94TPU CBQ6DqIR/hrai7q82Lb0qBphPooORSXraNus3dkjNehuRwroKdCp9BwDPNXYZQZjtt VyCSfNmpJmxQE8SIih2AmHQvdB+ArttO2Iy+BS6vJ+FD+B5wB7YtdEWRINnYBKkpqN BwUsMJ+plj4vk66H/GwspJ5HLkiQFv6+0HSil8jnlgT8WRpesFWM8A3k4SQna5XNI5 qE1P91tWqTu6TXXZ5994EXiU1Nlkv4eNyOIj0IJ2ixZVN24f5xqSaehfg/7lPnBx6G TwLsPX9P3V6hg== Received: from sofa.misterjones.org ([185.219.108.64] helo=lobster-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wz8Hb-00000001I3Q-1LLZ; Wed, 26 Aug 2026 07:42:51 +0000 Date: Wed, 26 Aug 2026 08:45:23 +0100 Message-ID: <874ighnx4c.wl-maz@kernel.org> From: Marc Zyngier To: syzbot Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, tglx@kernel.org Subject: Re: [syzbot] [kernel?] WARNING in gic_handle_irq In-Reply-To: <6a8de999.dbb3a75c.7844.002a.GAE@google.com> References: <6a8de999.dbb3a75c.7844.002a.GAE@google.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/30.1 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: syzbot+1e7fd72b380dc57b82b8@syzkaller.appspotmail.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, tglx@kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false On Tue, 25 Aug 2026 20:14:33 +0100, syzbot wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: 21d6ac051080 Merge branch 'for-next/core' into for-kernelci > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci > console output: https://syzkaller.appspot.com/x/log.txt?x=12f93e79580000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d1128bc53f2ef7f3 > dashboard link: https://syzkaller.appspot.com/bug?extid=1e7fd72b380dc57b82b8 > compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 > userspace arch: arm64 > > Unfortunately, I don't have any reproducer for this issue yet. > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/88380e2ddcb9/disk-21d6ac05.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/5dba5c2896b7/vmlinux-21d6ac05.xz > kernel image: https://storage.googleapis.com/syzbot-assets/52ac739e37e0/Image-21d6ac05.gz.xz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+1e7fd72b380dc57b82b8@syzkaller.appspotmail.com > > ------------[ cut here ]------------ > Unexpected interrupt (irqnr 8194) This appears to be triggered by an LPI (most probably an MSI) firing, but by the time we handle it, there is nothing to left handle it in the corresponding irq domain. The console log contains the following bits: [ 73.897524][ T1057] nvme nvme0: Identify namespace failed (-5) [ 73.906396][ T39] nvme nvme0: 2/0/0 default/read/poll queues [ 73.907149][ T7866] nvme nvme0: resetting controller [ 73.923113][ T866] usb 1-1: new high-speed USB device number 5 using dummy_hcd [ 73.943439][ T866] usb 1-1: device descriptor read/8, error -71 [ 73.986096][ C0] ------------[ cut here ]------------ [ 73.986109][ C0] Unexpected interrupt (irqnr 8194) which indicates that some stuff is being reset/failing close to that time. With the right timing (made easier with virtualisation), it isn't impossible to think that the interrupt has already reached the handling CPU while another CPU tears it down. Not sure there is anything to do here other than tone down the warning. M. -- Jazz isn't dead. It just smells funny.