From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Re: Regression on linux-next (next-20250321)
Date: Tue, 25 Mar 2025 10:43:17 -0300 [thread overview]
Message-ID: <Z+Ky9XsxHo/cECgr@nvidia.com> (raw)
In-Reply-To: <Z+Jd4GDIzCP5cBQE@nvidia.com>
On Tue, Mar 25, 2025 at 12:40:16AM -0700, Nicolin Chen wrote:
>
> On Tue, Mar 25, 2025 at 05:39:39AM +0000, Borah, Chaitanya Kumar wrote:
> > Hello Nicolin,
> >
> > Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
> >
> > This mail is regarding a regression we are seeing in our CI runs[1] on linux-next repository.
> >
> > Since the version next-20250321 [2], we are seeing the following regression
> >
> > `````````````````````````````````````````````````````````````````````````````````
> > <4>[ 0.226495] Unpatched return thunk in use. This should not happen!
> > <4>[ 0.226502] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/cpu/bugs.c:3107 __warn_thunk+0x62/0x70
>
> Hmm....I wonder why x86 can be affected...
I wonder if this is realted to the objtool warning Steven reported:
https://lore.kernel.org/linux-next/20250321193600.2bfe03bb@canb.auug.org.au/
vmlinux.o: warning: objtool: iommu_dma_get_msi_page() falls through to next function __iommu_dma_unmap()
I have no idea what either error means or how to fix it. AFAICT there
is nothing special about this patch to trigger this?
+Peter & Josh
Jason
next prev parent reply other threads:[~2025-03-25 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 5:39 Regression on linux-next (next-20250321) Borah, Chaitanya Kumar
2025-03-25 7:40 ` Nicolin Chen
2025-03-25 13:43 ` Jason Gunthorpe [this message]
2025-03-27 5:39 ` Josh Poimboeuf
2025-03-27 8:09 ` Borah, Chaitanya Kumar
2025-03-26 8:31 ` Borah, Chaitanya Kumar
2025-03-26 20:43 ` Nicolin Chen
2025-03-27 8:46 ` Borah, Chaitanya Kumar
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=Z+Ky9XsxHo/cECgr@nvidia.com \
--to=jgg@nvidia.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jani.saarinen@intel.com \
--cc=jpoimboe@kernel.org \
--cc=nicolinc@nvidia.com \
--cc=peterz@infradead.org \
--cc=suresh.kumar.kurmi@intel.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