[Driver][HIP] Fix bundled -S emitting bitcode instead of assembly for device (#189140)
[Driver][HIP] Fix bundled -S emitting bitcode instead of assembly for
device
PR #188262 added support for bundling HIP -S output under the new
offload driver, but the device backend still entered the
bitcode-emitting path in ConstructPhaseAction. The condition at the
Backend phase checked for the new offload driver and directed device
code to emit TY_LLVM_BC, without excluding the -S case. This caused
the device section in the bundled .s to contain LLVM bitcode instead
of textual AMDGPU assembly.
This broke the HIP UT CheckCodeObjAttr test which greps
copyKernel.s for "uniform_work_group_size" — a string that only
appears in textual assembly, not in bitcode.
Fix by excluding -S (without -emit-llvm) from the new-driver
bitcode path, so the device backend falls through to emit TY_PP_Asm
[3 lines not shown]
Merge tag 'hwmon-for-v7.0-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
Pull hwmon fixes from Guenter Roeck:
- PMBus driver fixes:
- Add mutex protection for regulator operations
- Fix reading from "write-only" attributes
- Mark lowest/average/highest/rated attributes as read-only
- isl68137: Add mutex protection for AVS enable sysfs attributes
- ina233: Fix error handling and sign extension when reading shunt voltage
- adm1177: Fix sysfs ABI violation and current unit conversion
- peci: Fix off-by-one in cputemp_is_visible(), and crit_hyst returning
delta instead of absolute temperature
* tag 'hwmon-for-v7.0-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
hwmon: (pmbus/core) Protect regulator operations with mutex
hwmon: (pmbus) Introduce the concept of "write-only" attributes
[6 lines not shown]
Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
Pull SCSI fixes from James Bottomley:
"Driver (and enclosure) only fixes. Most are obvious. The big change is
in the tcm_loop driver to add command draining to error handling (the
lack of which was causing hangs with the potential for double use
crashes)"
* tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
scsi: target: file: Use kzalloc_flex for aio_cmd
scsi: scsi_transport_sas: Fix the maximum channel scanning issue
scsi: target: tcm_loop: Drain commands in target_reset handler
scsi: ibmvfc: Fix OOB access in ibmvfc_discover_targets_done()
scsi: ses: Handle positive SCSI error from ses_recv_diag()
[XeVM] Fix the cache-control metadata string generation. (#187591)
Previously, it generated extra `single` quote marks around the outer
braces (i.e., `'{'` `6442:\220,1\22` `'}'`). SPIR-V backend does not
expect that. It expects `{6442:\220,1\22}`.
net: Fix build for custom kernel without loop interface
This is a follow-up fix to my previous commit
951ecd7f55e2edd33258ad6d9593c9f81c92b42e.
Tested with building the MINI64 kernel config.
Reported-by: swildner
AMDGPU: Make VarIndex WeakTrackingVH in AMDGPUPromoteAlloca (#188921)
The test used to look all good, but actually not. The WeakVH just make
itself null after the pointed value being replaced. So a zero value was
used because VarIndex become null. The test checks looks all good.
Actually only the WeakTrackingVH have the ability to be updated to new
value.
Change the test slightly to make that using zero index is wrong.
Clean up / re-factor trace and trap15:
- Everyone now gets a shared implementatio of trace and trap15 trap
handlers, largely based on the sun2/sun3 versions.
- Have a single copy of trap_kdebug() that calls KGDB, DDB, and a
machine-specific fallback hook (to accommodate the sun2/sun3
"give PROM a chance").
- The new shared trap_kdebug() is slightly different in that it takes
the trapframe argument by reference rather than by value, making it
easier to use as the back-end of ...
- ... oh hey look, a new shared straytrap() that also invokes trap_kdebug().
x11/nvidia-driver, x11/nvidia-kmod, x11/linux-nvidia-libs, graphics/nvidia-drm*-kmod, x11/nvidia-settings, x11/nvidia-xconfig: Update to 595.58.03
Update to latest Production Branch of drivers 595.58.03:
https://www.nvidia.com/en-us/drivers/details/265873/
Linux counterparts for x11/linux-nvidia-libs:
https://www.nvidia.com/en-us/drivers/details/265870/
Also bump -devel variant to match with master ports, as Production
Branch [PB] of drivers have now higher version than New Feature
Branch [NFB] of drivers.
As this update drops a bunch of old (pre-Turing generation of
architectures) GPUs as done in -devel variants updated 20260103,
add -580 variant of legacy branch of driver.
Currently, this is exactly the same version before this update.
(580.142)
[2 lines not shown]
Update to 0.62
Upstream changes:
0.62 - 2025-01-13, H.Merijn Brand
* doc should not be part of test
0.61 - 2025-01-13, H.Merijn Brand
* Replace "use vars" with "our" (James Raspass: PR #9)
* Specify recommended versions based on known CVE's
* Update doc for groff-1.24
* It's 2024
* Tested with perl-5.40.0
* It's 2025
* Add SECURITY.md
Merge tag 'drm-fixes-2026-03-28-1' of https://gitlab.freedesktop.org/drm/kernel
Pull drm fixes from Dave Airlie:
"Weekly fixes, still a bit busy, but the usual suspects amdgpu and
i915/xe have a bunch of small fixes, and otherwise it's just a few
minor driver fixes.
loognsoon:
- update MAINTAINERS
shmem:
- fault handler fix
syncobj:
- fix GFP flags
amdgpu:
- DSC fix
- Module parameter parsing fix
[50 lines not shown]
www/fabio: Update 1.6.4 => 1.6.11, fix runtime
A recent update to Consul causes Fabio to fail to register itself in the
service directory. Consul has apparently become stricter in its
interpretation of IPv4 addresses and fails to recognize an IPv4 address
surrounded by square brackets. Versions prior to 1.22 permitted this.
Fabio (prior to 1.6.11) sends its IPv4 address wrapped in square
brackets and will fail to register on a newer Consul.
Changelog:
https://github.com/fabiolb/fabio/blob/master/CHANGELOG.md#v1611-2025-12-09
While here replace PORTVERSION with DISTVERSION.
PR: 294048
Approved by: blanket (fix runtime)
Sponsored by: UNIS Labs
MFH: 2026Q1
(cherry picked from commit ea4da10cbbcac68e7befde5375f2650a2e81b836)
[Clang] remove redundant uses of dyn_cast (NFC) (#189106)
This removes dyn_cast invocations where the argument is already of the
target type (including through subtyping). This was created by adding a
static assert in dyn_cast and letting an LLM iterate until the code base
compiled. I then went through each example and cleaned it up. This does
not commit the static assert in dyn_cast, because it would prevent a lot
of uses in templated code. To prevent backsliding we should instead add
an LLVM aware version of
https://clang.llvm.org/extra/clang-tidy/checks/readability/redundant-casting.html
(or expand the existing one).
www/fabio: Update 1.6.4 => 1.6.11, fix runtime
A recent update to Consul causes Fabio to fail to register itself in the
service directory. Consul has apparently become stricter in its
interpretation of IPv4 addresses and fails to recognize an IPv4 address
surrounded by square brackets. Versions prior to 1.22 permitted this.
Fabio (prior to 1.6.11) sends its IPv4 address wrapped in square
brackets and will fail to register on a newer Consul.
Changelog:
https://github.com/fabiolb/fabio/blob/master/CHANGELOG.md#v1611-2025-12-09
While here replace PORTVERSION with DISTVERSION.
PR: 294048
Approved by: blanket (fix runtime)
Sponsored by: UNIS Labs
MFH: 2026Q1
