[CIR][NFC] Add missing dependency for CIR dialect (#234042)
https://github.com/llvm/llvm-project/pull/229494 introduced a build
dependency on TargetParser in the MLIRCIR component but didn't add it as
a link component. This causes link failures when building with shared
libraries. This change adds the link component.
Add layout parameter to sharing.s3
Add a new create-time-only field to sharing.s3 `layout` that indicates
whether the specified share is used as a normal truenas S3 bucket,
which implies a certain directory structure `s3data` contains the
live data export and `.truenas_s3` contains a side tree with versions,
in-progress multipart uploads, etc. Or a "whole dataset" bucket.
Whole dataset buckets are readonly and are used for cases where
administrators wish to export existing RW NFS / SMB shares over
S3 in a readonly manner.
The configuration knob used to determine the type of bucket to
be created (and once again, this is create-time only), is the
new `layout` parameter that supports two values:
* BUCKET - a conventional S3 oriented bucket that may optionally
be exported RO via NFS / SMB
[2 lines not shown]
[compiler-rt][Darwin] Disable the armv7* sanitizer slices for watchOS
armv7* are no longer supported for watchOS, stop building them.
Co-Authored-By: Claude
rdar://182837745
[CIR] Make sure we properly set the VFS in ClangIR (#234040)
CIR pre-commit CI started failing due to #233475, which is because
ClangIR failed to set up the virtual file system. There are a handful of
locations that look about right for this, however setting it right here,
immediately after the diagnostic-handler is set, best mirrors what
CodeGenAction.cpp does.
This should unblock CI for ClangIR on the
inline-asm-backend-diagnostic.c test.
[compiler-rt][Darwin] Support building sanitizers for visionOS
COMPILER_RT_ENABLE_XROS previously only enabled builtins. Teach
config-ix.cmake about the xros/xrossim platforms so the
sanitizer runtimes are configured for them as well.
Co-Authored-By: Claude
rdar://190575578
Add the WHOLE_DATASET layout to sharing.s3
Before: sharing.s3.create always created a new dataset. The S3 service
wrote s3data/ and .truenas_s3/ on it. There was no way to serve an
existing dataset over S3. Every share and every writing task on a
bucket's dataset was refused unless it was s3data read-only.
Now:
- SharingS3Entry has `layout`: BUCKET (the default, unchanged) or
WHOLE_DATASET. The field is create-only. The update model excludes
it. The v27_0_0 and v28_0_0 models both carry it, because the
change ships in 27.0 too.
- A new `layout` column stores it. The migration is bbce11d3cbd7
under 27.0, as it ships on 27.0. Master gets a merge migration
(9a4e61c0f2d7) that joins it to the 28.0 chain. Existing rows read
as BUCKET.
- A WHOLE_DATASET create uses the dataset named in `dataset`. Nothing
is created, set or written on that dataset. A failed create does not
[26 lines not shown]
NAS-144375 / 27.0.0 / Always write INFO/version when storing an SMB share ACL (by anodos325) (#19985)
store_share_acl only wrote the INFO/version key into share_info.tdb when
the file did not exist. This fixes a regression introduced when we added
stateful failover for SMB to truenas 26 and adds test coverage.
Original PR: https://github.com/truenas/middleware/pull/19983
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
Merge tag 'chrome-platform-firmware-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux
Pull chrome platform firmware loader updates from Tzung-Bi Shih:
"New:
- Rename drivers/firmware/google/ -> drivers/firmware/coreboot/ and
corresponding Kconfig names
- Separate firmware_attributes_class from drivers/platform/x86/ to
drivers/firmware/ so that it is available for non-x86 platforms
- Add CFR (coreboot form representation) driver to expose the
attributes via sysfs
Improvements:
- Use named initializers for acpi_device_id"
* tag 'chrome-platform-firmware-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux:
firmware: coreboot: Add CFR firmware attributes driver
firmware: Move firmware attributes class helper
firmware: coreboot: Use named initializers for acpi_device_id
firmware: Rename google firmware directory to coreboot
Merge tag 'chrome-platform-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux
Pull chrome platform updates from Tzung-Bi Shih:
"Improvements:
- Poll for role swap completion in cros_ec_typec
Fixes:
- Fix wrong returned data and length for deferred response in
transport protocol
- Check boundary for EC-returned data length in cros_ec_typec
- Fix a regression for older ChromeOS devices after applying
db65a06d10b3 ("ACPI: EC: Convert the driver to a platform one")
Cleanups:
- Fix typos"
* tag 'chrome-platform-v7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux:
platform/chrome: cros_ec_typec: Poll for role swap completion
platform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004
[6 lines not shown]
Merge tag 'cmpxchg-emu.2026.10.12b' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
Pull two-byte cmpxchg emulation from Paul McKenney:
"These commits add a cmpxchg_emu_u16() function that emulates two-byte
cmpxchg() in terms of four-byte cmpxchg() for architectures not having
native instructions for this purpose. They also make use of this
cmpxchg_emu_u16() function in those architectures, namely sh, arc,
csky, and xtensa. This permits use of two-byte cmpxchg() in common
code.
However, it sadly does not permit easy implementation of all
algorithms needing on two-byte atomic operations because there are
some systems still supported by Linux that do not have native two-byte
store instructions.
There is reason to believe that these systems will soon no longer be
supported by Linux [1]"
Link: https://lore.kernel.org/all/20260908152808.3928630-4-arnd@kernel.org/ [1]
[7 lines not shown]
[RISCV][P-ext] Check the range of the timm in USATI/SATI isel patterns. (#233963)
#233769 is adding intrinsics for these operations. The immediate range
will be checked in clang, but clang isn't the only frontend. Protect the
isel patterns so they will generate a "cannot select" error.
[BOLT] Fix data race in CDSplit
There is a race in split functions pass, CDSplit strategy, that might
affect production although it is not super common. We've observed only
a few cases in one workload. The problem is that one thread might be
inserting new basic blocks in a function (BF object) while another is
trying to read the blocks via BF::front(). If the threads are timed
in the wrong way, the reading thread will load an invalid pointer and
crash on DstBB->getKnownExecutionCount(). The BB insertion is done by
SplitFunctions to insert EH trampolines.
database/p5-DBI: update to 1.656
1.656 (2026-10-17)
* Re-add conflicts to cpanfile. (WIP)
* Remove lock file on end of scope
* Prevent dbi_profile crash (CVE-2026-108518) (Henrik Teichmann)
* Memory corruption via selectrow_array + SQLite UDF (issue#98)
* Fix errstr when dbm_updatable_key attribute for DBD::DBM is set to 2
(croak) on Perl versions < v5.13.2.
* Fix emit warnings when dbm_updatable_key attribute for DBD::DBM is set to
1 (carp)
* Fix lock file not removed when DBD::DBM check for bad serializer class
fails. (CVE-2026-111879)
* *** WARNING: Next release will require perl-5.14 ***
- Main reason: Exception handling
Merge tag 'docs-7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/docs/linux
Pull documentation updates from Jonathan Corbet:
"It was a reasonably busy cycle for docs; changes include:
- Add the AGENTS.md symbolic link into the top-level directory in the
hopes that LLMs will read it and produce better work
- The removal of the Assisted-by requirement, as concluded at the
Maintainer Summit
- A new "testdocs" make target to run the documentation unit tests
- Lots of work on the Portuguese, and Chinese translations; there is
now maintenance for the traditional Chinese translations as well
...and the usual pile of minor fixes, documentation updates, etc"
* tag 'docs-7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/docs/linux: (125 commits)
[21 lines not shown]
[libc][cmake] Respect the configured optimization level for memory functions (#233920)
`add_implementation` unconditionally passes `${libc_opt_high_flag}`
(`-O3`) to the memory functions (`memcpy`, `memmove`, `memset`,
`memcmp`, `bcmp`, `bzero`), overriding `-Os` in `MinSizeRel` builds.
Drop the override so these functions respect the optimization level
configured by CMake like the rest of the library.
Merge tag 'nolibc-20261018-for-7.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc
Pull nolibc updates from Thomas Weißschuh:
- New architectures: Hexagon, 64-bit parisc
- New library functionality: sendfile(), pread(), pwrite()
- Various bugfixes and cleanups
* tag 'nolibc-20261018-for-7.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc: (28 commits)
selftests/nolibc: explicitly disable position independent executables
selftests/nolibc: use the configured kernel header directory
tools/nolibc: fix the function argument order of calloc()
tools/nolibc: check for overflow in malloc()
tools/nolibc: stop rounding malloc() sizes up to 4096 bytes
tools/nolibc: add support for pread() and pwrite()
tools/nolibc: introduce __NOLIBC_BITS_PER_SYSCALL_ARG
tools/nolibc: move __NOLIBC_LLARGPART() to compiler.h
[13 lines not shown]
[AArch64] Test the i32 preserve_none argument registers on Windows (#234019)
CC_AArch64_Preserve_None excludes X15 from the argument registers on
Windows, where it is used for stack allocation, but only the i64 case
was covered by preserve_nonecc_call.ll. Add the i32 counterpart: the 24th
i32 argument is passed in w15 on AAPCS and Darwin targets and on the stack
on Windows.
Assisted-by: Claude
Merge tag 'for-linus-7.4-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
Pull xen updates from Juergen Gross:
"This time only small fixes and cleanups all over Xen related drivers.
Nothing really stands out here"
* tag 'for-linus-7.4-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
xen-blkfront: Fix IO race during unplug
xen-pciback: Fix pcistub_device ref leak in pcistub_get_gsi_from_sbdf()
xen/pcifront: check that an AER callback exists before calling it
xen/gntdev: Fix gntdev_dmabuf ref leak in dmabuf_exp_wait_released()
x86/PVH: don't truncate initrd address/size
xen/privcmd: Only claim ioreqs matching an ioeventfd
xen/scsifront: check for a NULL shadow entry on a backend response
xen: fix typos in comments
xen/gntdev: prevent private mappings from becoming writable
xen: remove unused hvm_vcpu.h header
xen-blkfront: unbind irq before tearing down ring and shadow requests
xen/blkback: Prevent missed completion when draining I/O
xen/pcifront: Fix PCI device reference leak in AER handling
