From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com, Guenter Roeck <linux@roeck-us.net>,
Matt Turner <mattst88@gmail.com>
Subject: Re: [PATCH 5.15 000/935] 5.15.221-rc1 review
Date: Fri, 18 Sep 2026 15:45:41 -0400 [thread overview]
Message-ID: <2026-09-18-daily-reply-0014-re-alpha-fp-exception-bits@kernel.org> (raw)
In-Reply-To: <d08261fc-605f-4ed6-b7f0-b9575c2de55c@roeck-us.net>
> All alpha images:
>
> Error log:
> arch/alpha/kernel/traps.c: In function 'do_entIF':
> arch/alpha/kernel/traps.c:373:35: error: too few arguments to function 'alpha_fp_emul'
> 373 | si_code = alpha_fp_emul(regs->pc - 4);
>
> This affects v5.15.221, v6.1.188, and v6.6.157.
Reverted on 6.6, 6.1 and 5.15, along with 49672d026cc4 ("alpha: fix
ieee_swcr_to_fpcr setting FPCR_DNOD unconditionally"), since both changelogs
say the two must not be separated. 7.2, 6.18 and 6.12 are unaffected: the
second call site lives in do_entIF(), which only exists on trees predating
a4184174be36 ("alpha: drop pre-EV56 support").
Matt, could you send a version of bcfe3187412e ("alpha: don't leak
hardware-fabricated FP exception bits to user space") for 5.15, 6.1 and 6.6
that updates the do_entIF() call site as well? Otherwise the fix stays out of
those three trees.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-18 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 6:50 Greg Kroah-Hartman
2026-09-12 17:43 ` Brett A C Sheffield
2026-09-12 18:07 ` Barry K. Nathan
[not found] ` <82fb64b5-4273-4cb3-be34-ed9fd2d0dd94@w6rz.net>
2026-09-13 11:26 ` Sasha Levin
2026-09-13 23:23 ` Ron Economos
2026-09-14 17:26 ` Florian Fainelli
[not found] ` <20260912065546.976652519@linuxfoundation.org>
[not found] ` <20260913202907.3100-1-kmehltretter@gmail.com>
2026-09-17 4:00 ` [PATCH 5.15.y 0/2] Bluetooth: L2CAP: fix connectionless receive path Karl Mehltretter
2026-09-17 4:00 ` [PATCH 5.15.y 1/2] Bluetooth: L2CAP: Fix deadlock Karl Mehltretter
2026-09-17 4:00 ` [PATCH 5.15.y 2/2] bluetooth/l2cap: sync sock recv cb and release Karl Mehltretter
2026-09-18 0:52 ` [PATCH 5.15.y 0/2] Bluetooth: L2CAP: fix connectionless receive path Sasha Levin
2026-09-18 4:28 ` [PATCH 5.15 000/935] 5.15.221-rc1 review Guenter Roeck
2026-09-18 19:45 ` Sasha Levin [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=2026-09-18-daily-reply-0014-re-alpha-fp-exception-bits@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mattst88@gmail.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®