From 36fdc30799abaf11f38173ad715adf07ee9a2921 Mon Sep 17 00:00:00 2001 From: Rory Li <736729045@qq.com> Date: Sun, 27 Oct 2024 11:18:25 +0000 Subject: [PATCH] update news/README.md. Signed-off-by: Rory Li <736729045@qq.com> --- news/README.md | 713 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 713 insertions(+) diff --git a/news/README.md b/news/README.md index 9867dee..e1728cb 100644 --- a/news/README.md +++ b/news/README.md @@ -7,6 +7,719 @@ * [2023 年 - 下半年](2023-2nd-half.md) * [2024 年 - 上半年](2024-1st-half.md) +## 20241027：第 115 期 + +### 内核动态 + +#### RISC-V 架构支持 + +**[v1: riscv: Relocatable NOMMU kernels](http://lore.kernel.org/linux-riscv/20241026171441.3047904-1-samuel.holland@sifive.com/)** + +> Currently, RISC-V NOMMU kernels are linked at CONFIG_PAGE_OFFSET, and +> since they are not relocatable, must be loaded at this address as well. + +**[v3: bpf-next: Optimize bpf_csum_diff() and homogenize for all archs](http://lore.kernel.org/linux-riscv/20241026125339.26459-1-puranjay@kernel.org/)** + +**[v1: Prefer sysfs/JSON events also when no PMU is provided](http://lore.kernel.org/linux-riscv/20241026121758.143259-1-irogers@google.com/)** + +> At the RISC-V summit the topic of avoiding event data being in the +> RISC-V PMU kernel driver came up. There is a preference for sysfs/JSON +> events being the priority when no PMU is provided so that legacy +> events maybe supported via json. + +**[v2: Wire up CRC32 library functions to arch-optimized code](http://lore.kernel.org/linux-riscv/20241025191454.72616-1-ebiggers@kernel.org/)** + +> This patchset fixes that so that the CRC32 library functions use the +> optimized code. This allows users to just use the library instead of +> the crypto API. + +**[v5: net-next: Add the dwmac driver support for T-HEAD TH1520 SoC](http://lore.kernel.org/linux-riscv/20241025-th1520-gmac-v5-0-38d0a48406ff@tenstorrent.com/)** + +> This series adds support for dwmac gigabit ethernet in the T-Head TH1520 +> RISC-V SoC used on boards like BeagleV Ahead and the LicheePi 4A. + +**[v2: Add Microchip IPC mailbox](http://lore.kernel.org/linux-riscv/20241025125110.1347757-1-valentina.fernandezalanis@microchip.com/)** + +> This series adds support for the Microchip Inter-Processor Communication +> (IPC) mailbox driver. + +**[v1: RISC-V: Enable Zicbom in usermode](http://lore.kernel.org/linux-riscv/20241025091527.57825-1-cuiyunhui@bytedance.com/)** + +> Like Zicboz, by enabling the corresponding bits of senvcfg, +> the instructions cbo.clean, cbo.flush, and cbo.inval can be +> executed normally in user mode. + +**[v5: pwm: Add pwm driver for Sophgo SG2042](http://lore.kernel.org/linux-riscv/cover.1729843087.git.unicorn_wang@outlook.com/)** + +> Add driver for pwm controller of Sophgo SG2042 SoC. + +**[v2: riscv: sophgo: Add ethernet support for SG2044](http://lore.kernel.org/linux-riscv/20241025011000.244350-1-inochiama@gmail.com/)** + +> The ethernet controller of SG2044 is Synopsys DesignWare IP with +> custom clock. Add glue layer for it. + +**[v1: perf, riscv: Wire up perf trace support for RISC-V](http://lore.kernel.org/linux-riscv/20241024190353.46737-1-bjorn@kernel.org/)** + +> RISC-V does not currently support perf trace, since the system call +> table is not generated. + +**[v2: Add some validation for vector, vector crypto and fp stuff](http://lore.kernel.org/linux-riscv/20241024-fanning-enrage-bcc39f8ed47d@spud/)** + +> This series is partly leveraging Clement's work adding a validate +> callback in the extension detection code so that things like checking +> for whether a vector crypto extension is usable can be done like: +> has_extension() +> rather than +> has_vector() && has_extension() +> which Eric pointed out was a poor design some months ago. + +**[v1: riscv: sophgo: Add pinctrl support for SG2042](http://lore.kernel.org/linux-riscv/20241024064356.865055-1-inochiama@gmail.com/)** + +> Add support for SG2042 pinctrl device. + +**[v2: of/fdt: add dt_phys arg to early_init_dt_scan and early_init_dt_verify](http://lore.kernel.org/linux-riscv/20241023171426.452688-1-usamaarif642@gmail.com/)** + +> Hence save the physical address when it is known at +> boot time when calling early_init_dt_scan for arm64 and use it at kexec +> time instead of converting the virtual address using __pa(). + +**[v4: riscv: interrupt-controller: Add T-HEAD C900 ACLINT SSWI](http://lore.kernel.org/linux-riscv/20241022040218.450573-1-inochiama@gmail.com/)** + +> New version of T-HEAD C920 implement a fully featured ACLINT[1] device +> (This core is used by Sophgo SG2044). This ACLINT device provides a +> SSWI field to support fast S-mode IPI. Add full support for T-HEAD C900 SSWI device. + +**[v2: kasan: RISC-V support for KASAN_SW_TAGS using pointer masking](http://lore.kernel.org/linux-riscv/20241022015913.3524425-1-samuel.holland@sifive.com/)** + +> This series implements support for software tag-based KASAN using the +> RISC-V pointer masking extension[1], which supports 7 and/or 16-bit +> tags. + +**[v2: serial: 8250_dw: Introduce SG2044 uart support.](http://lore.kernel.org/linux-riscv/20241021072606.585878-1-inochiama@gmail.com/)** + +> SG2044 relys on an internal divisor when calculating bitrate, which +> means a wrong clock for the most common bitrates. + +**[v2: Accelerate KVM RISC-V when running as a guest](http://lore.kernel.org/linux-riscv/20241020194734.58686-1-apatel@ventanamicro.com/)** + +> The KVM RISC-V hypervisor might be running as a guest under some other +> host hypervisor in which case the complete H-extension functionality will +> be trap-n-emulated by the host hypervisor. + +**[GIT PULL: RISC-V T-HEAD Devicetrees for v6.13](http://lore.kernel.org/linux-riscv/ZxUVVk9gWJAVrp0g@x1/)** + +**[v1: mmc: dw_mmc: take SWIOTLB memory size limitation into account](http://lore.kernel.org/linux-riscv/20241020142931.138277-1-aurelien@aurel32.net/)** + +> The Synopsys DesignWare mmc controller on the JH7110 SoC +> (dw_mmc-starfive.c driver) is using a 32-bit IDMAC address bus width, +> and thus requires the use of SWIOTLB. + +**[v5: Add DeepComputing FML13V01 board dts](http://lore.kernel.org/linux-riscv/20241020134959.519462-1-guodong@riscstar.com/)** + +> This series updates Device Tree related files to introduce the +> FML13V10 board from DeepComputing, which incorporates a StarFive +> JH7110 SoC. This board is designed for use on the Framework Laptop 13 +> Chassis, which has (Framework) SKU FRANHQ0001. + +#### LoongArch 架构支持 + +**[v10: Replace fallback for IO memcpy and IO memset](http://lore.kernel.org/loongarch/20241021133154.516847-1-jvetter@kalrayinc.com/)** + +> I have updated the +> patchset, and placed the functions directly in asm-generic/io.h. + +#### ARM 架构支持 + +**[v3: Add support for Exynos9810 SoC and Samsung Galaxy S9 (SM-G960F)](http://lore.kernel.org/linux-arm-kernel/20241026-exynos9810-v3-0-b89de9441ea8@gmail.com/)** + +> This series adds initial SoC support for the Samsung Exynos 9810 +> SoC and initial board support for Samsung Galaxy S9 phone (SM-G960F), +> codenamed starlte. + +**[v1: arm_pmuv3: Add support for Samsung Mongoose PMU](http://lore.kernel.org/linux-arm-kernel/20241026-mongoose-pmu-v1-0-f1a7448054be@gmail.com/)** + +> This series adds support to performance monitoring unit of +> the Samsung Mongoose CPU cores. They were released between +> such as Exynos 8890, 8895, 9810, 9820 and 990 (9830). + +**[v5: iommufd: Add vIOMMU infrastructure (Part-2: vDEVICE)](http://lore.kernel.org/linux-arm-kernel/cover.1729897278.git.nicolinc@nvidia.com/)** + +> Following the previous vIOMMU series, this adds another vDEVICE structure, +> representing the association from an iommufd_device to an iommufd_viommu. + +**[v5: iommufd: Add vIOMMU infrastructure (Part-1)](http://lore.kernel.org/linux-arm-kernel/cover.1729897352.git.nicolinc@nvidia.com/)** + +> This series introduces a new vIOMMU infrastructure and related ioctls. + +**[v1: KVM: arm64: Mark the VM as dead for failed initializations](http://lore.kernel.org/linux-arm-kernel/20241025221220.2985227-1-rananta@google.com/)** + +> Syzbot hit the following WARN_ON() in kvm_timer_update_irq(): + +**[v1: perf arm-spe: Allow synthesizing of branch](http://lore.kernel.org/linux-arm-kernel/20241025143009.25419-1-graham.woodward@arm.com/)** + +**[v1: Add device tree for MT8188-based Chromebook "Ciri"](http://lore.kernel.org/linux-arm-kernel/20241025110111.1321704-1-fshao@chromium.org/)** + +> This series introduces the device trees for Ciri, a MT8188-based +> Chromebook, commercially known as the Lenovo Chromebook Duet (11", 9). + +**[v1: clk: sunxi-ng: h616: Reparent CPU clock during frequency changes](http://lore.kernel.org/linux-arm-kernel/20241025105620.1891596-1-andre.przywara@arm.com/)** + +> The H616 user manual recommends to re-parent the CPU clock during +> frequency changes of the PLL, and recommends PLL_PERI0(1X), which runs +> at 600 MHz. + +**[v2: KVM: arm64: Errata management for VM Live migration](http://lore.kernel.org/linux-arm-kernel/20241024094012.29452-1-shameerali.kolothum.thodi@huawei.com/)** + +> This is another attempt on this based on the feedback received +> for RFC v1. Thanks for all the discussions and suggestions. + +**[v1: Add MediaTek APU SMC call Definition](http://lore.kernel.org/linux-arm-kernel/20241024092712.431605-1-karl.li@mediatek.com/)** + +> This patch introduces the SMC calls for MediaTek APU. + +**[v4: source filtering for multi-port output](http://lore.kernel.org/linux-arm-kernel/20241024065306.14647-1-quic_taozha@quicinc.com/)** + +> In our hardware design, by combining a funnel and a replicator, it +> implement a hardware device with one-to-one correspondence between +> output ports and input ports. + +**[v2: net-next: net: sparx5: add support for lan969x switch device](http://lore.kernel.org/linux-arm-kernel/20241024-sparx5-lan969x-switch-driver-2-v2-0-a0b5fae88a0f@microchip.com/)** + +> This series is the second of a multi-part series, that prepares and adds +> support for the new lan969x switch driver. + +#### X86 架构支持 + +**[GIT PULL: platform-drivers-x86 for 6.12-3](http://lore.kernel.org/lkml/b220d6bc-41da-4ae6-8f69-4f008f15d540@redhat.com/)** + +> Here is the second round of fixes for platform-drivers-x86 for 6.12. + +**[v1: perf cap: Add __NR_capget to arch/x86 unistd](http://lore.kernel.org/lkml/20241026055448.312247-1-irogers@google.com/)** + +> As there are duplicated kernel headers in tools/include libc can pick +> up the wrong definitions. This was causing the wrong system call for +> capget in perf. + +**[v1: Mypy and pylint build support](http://lore.kernel.org/lkml/20241025172303.77538-1-irogers@google.com/)** + +> Support building perf checking the python code with mypy and/or +> pylint. Currently there are too many errors to make this a default. + +**[v4: x86 Heterogeneous design identification](http://lore.kernel.org/lkml/20241025171459.1093-1-mario.limonciello@amd.com/)** + +> This series adds topology identification for Intel and AMD processors and +> uses this identification in the AMD CPPC code to identify the boost +> numerator. + +**[v9: Dell AWCC platform_profile support](http://lore.kernel.org/lkml/20241025150916.3618-2-kuurtb@gmail.com/)** + +> This patch adds platform_profile support for Dell devices which implement +> WMAX thermal interface, that are meant to be controlled by Alienware Command +> Center (AWCC). + +**[v1: net-next: Mitigate the two-reallocations issue for iptunnels](http://lore.kernel.org/lkml/20241025133727.27742-1-justin.iurman@uliege.be/)** + +> The same pattern is found in ioam6, rpl6, and seg6. Basically, it first +> makes sure there is enough room for inserting a new header. + +**[v6: Add RAPL core energy counter support for AMD CPUs](http://lore.kernel.org/lkml/20241025111348.3810-1-Dhananjay.Ugwekar@amd.com/)** + +> This patchset adds a new "power_core" PMU alongside the existing +> "power" PMU, which will be responsible for collecting the new +> "energy-core" event. + +**[v1: mfd: intel_soc_pmic_crc: Add support for non ACPI instantiated i2c_client](http://lore.kernel.org/lkml/20241025083712.15070-1-hdegoede@redhat.com/)** + +> Add an i2c_device_id table so that the driver can match on manually +> instantiated i2c_client-s (which lack an ACPI fwnode to match on). + +**[v5: Add AutoFDO and Propeller support for Clang build](http://lore.kernel.org/lkml/20241023224409.201771-1-xur@google.com/)** + +> This patch series is to integrate AutoFDO and Propeller support into +> the Linux kernel. + +**[v4: Provide support for RMPREAD and a segmented RMP](http://lore.kernel.org/lkml/cover.1729708922.git.thomas.lendacky@amd.com/)** + +> This series adds SEV-SNP support for a new instruction to read an RMP +> entry and for a segmented RMP table. + +**[v1: AMD NB and SMN rework](http://lore.kernel.org/lkml/20241023172150.659002-1-yazen.ghannam@amd.com/)** + +> The theme of this set is decoupling the "AMD node" concept from the +> legacy northbridge support. + +**[v2: drm-dp: Add dp module in hibmc driver](http://lore.kernel.org/lkml/20241022124148.1952761-1-shiyongbang@huawei.com/)** + +> Realizing the basic display function of DP cable for DP connector +> displaying. Add DP module in hibmc drm driver, which is for Hisilicon +> Hibmc SoC which used for Out-of-band management. + +#### 进程调度 + +**[v1: sched/topology: Enable topology_span_sane check only for debug builds](http://lore.kernel.org/lkml/1729619853-2597-1-git-send-email-ssengar@linux.microsoft.com/)** + +> On a x86 system under test with 1780 CPUs, topology_span_sane() takes +> around 8 seconds cumulatively for all the iterations. It is an expensive +> operation which does the sanity of non-NUMA topology masks. + +**[GIT PULL: sched/urgent for v6.12-rc4](http://lore.kernel.org/lkml/20241020104957.GAZxTgVRnWOwSC1EnE@fat_crate.local/)** + +#### 内存管理 + +**[v1: mm: count zeromap read and set for swapout and swapin](http://lore.kernel.org/linux-mm/20241027011959.9226-1-21cnbao@gmail.com/)** + +> When the proportion of folios from the zero map is small, missing their +> accounting may not significantly impact profiling. +> This patch adopts option 2. I'm curious if others have different +> opinions, so I'm marking it as RFC. + +**[v1: mm: mitigate large folios usage and swap thrashing for nearly full memcg](http://lore.kernel.org/linux-mm/20241027001444.3233-1-21cnbao@gmail.com/)** + +> The issue arises from an edge case where the memory cgroup remains +> nearly full most of the time. + +**[v2: mm: shmem: fallback to page size splice if large folio has poisoned pages](http://lore.kernel.org/linux-mm/e3737fbd5366c4de4337bf5f2044817e77a5235b.1729915173.git.baolin.wang@linux.alibaba.com/)** + +> Thus adding a fallback to the PAGE_SIZE splice() still allows reading +> normal pages if the large folio has hwpoisoned pages. + +**[v1: -next: memcg: factor out mem_cgroup_stat_aggregate()](http://lore.kernel.org/linux-mm/20241026093407.310955-1-xiujianfeng@huaweicloud.com/)** + +> Currently mem_cgroup_css_rstat_flush() is used to flush the per-CPU +> statistics from a specified CPU into the global statistics of the +> memcg. + +**[v1: mm: add per-order mTHP swpin counters](http://lore.kernel.org/linux-mm/20241026082423.26298-1-21cnbao@gmail.com/)** + +> This helps profile the sizes of folios being swapped in. Currently, +> only mTHP swap-out is being counted. + +**[v6: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-mm/cover.1729926229.git.lorenzo.stoakes@oracle.com/)** + +> This series introduces sentinels for this purposes which can be passed as +> the pidfd in this instance rather than having to establish a dummy fd for +> this purpose. + +**[v2: mm-unstable: mm/page_alloc: keep track of free highatomic](http://lore.kernel.org/linux-mm/20241026033625.2237102-1-yuzhao@google.com/)** + +> And the third line shows there were no free pages in any +> MIGRATE_HIGHATOMIC pageblocks, which otherwise would show up as type +> 'H'. + +**[v2: 0/2: memcg: tracepoint for flushing stats](http://lore.kernel.org/linux-mm/20241026004826.55351-1-inwardvessel@gmail.com/)** + +> This tracepoint gives visibility on how often the flushing of memcg stats +> occurs and contains info on whether it was forced, skipped, and the value +> of stats updated. + +**[v2: netfs: Read performance improvements and "single-blob" support](http://lore.kernel.org/linux-mm/20241025204008.4076565-1-dhowells@redhat.com/)** + +> This set of patches is primarily about two things: improving read +> performance and supporting monolithic single-blob objects that have to be +> read/written as such (e.g. AFS directory contents). The implementation of +> the two parts is interwoven as each makes the other possible. + +**[v14: EDAC: Scrub: introduce generic EDAC RAS control feature driver + CXL/ACPI-RAS2 drivers](http://lore.kernel.org/linux-mm/20241025171356.1377-1-shiju.jose@huawei.com/)** + +> Previously known as "ras: scrub: introduce subsystem + CXL/ACPI-RAS2 drivers". + +**[v1: fs/proc/vmcore: kdump support for virtio-mem on s390](http://lore.kernel.org/linux-mm/20241025151134.1275575-1-david@redhat.com/)** + +> This is based on "v3: virtio-mem: s390 support" [1], which adds +> virtio-mem support on s390. + +**[v5: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-mm/cover.1729848252.git.lorenzo.stoakes@oracle.com/)** + +> This series introduces sentinels for this purposes which can be passed as +> the pidfd in this instance rather than having to establish a dummy fd for +> this purpose. + +**[v1: futex: The remaining futex2 bits](http://lore.kernel.org/linux-mm/20241025090347.244183920@infradead.org/)** + +> By popular demand a repost of the remaining futex2 bits. + +**[v1: mm: shmem: fallback to page size splice if large folio has poisoned subpages](http://lore.kernel.org/linux-mm/fd3893f318493a3720dc1a4b1c33f0f692ddf125.1729825743.git.baolin.wang@linux.alibaba.com/)** + +> The tmpfs has already supported the PMD-sized large folios, and splice() +> can not read any subpages if the large folio has a poisoned subpage, +> which is not good as we discussed in previous mail[1]. + +**[v1: mm/vma: miss to restore vmi.index on expansion failure](http://lore.kernel.org/linux-mm/20241025031847.6274-1-richard.weiyang@gmail.com/)** + +> This serial starts on spotting on miss to restore vmi.index in +> vma_merge_new_range() when expansion is failed. + +**[v1: memcg-v1: fully deprecate charge moving](http://lore.kernel.org/linux-mm/20241025012304.2473312-1-shakeel.butt@linux.dev/)** + +> This warning has +> been backported to all stable kernel and there have not been any report +> of the warning or the request to support this feature anymore. + +**[v1: memcg: tracepoint for flushing stats](http://lore.kernel.org/linux-mm/20241025002511.129899-1-inwardvessel@gmail.com/)** + +> This tracepoint gives visibility on how often the flushing of memcg stats +> occurs, along with the reason for the flush. + +**[v2: mm/vma: the pgoff is correct if can_merge_right](http://lore.kernel.org/linux-mm/20241024093347.18057-1-richard.weiyang@gmail.com/)** + +> By this point can_vma_merge_right() must have returned true, which implies +> can_vma_merge_before() also returned true, which already asserts that the +> pgoff is as expected for a merge with the following VMA, thus this +> assignment is redundant. + +#### 文件系统 + +**[v6: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-fsdevel/cover.1729926229.git.lorenzo.stoakes@oracle.com/)** + +> This series introduces sentinels for this purposes which can be passed as +> the pidfd in this instance rather than having to establish a dummy fd for +> this purpose. + +**[v1: xfs: Do not fallback to buffered-io for DIO atomic write](http://lore.kernel.org/linux-fsdevel/627c14b7987a3ab91d9bff31b99d86167d56f476.1729879630.git.ritesh.list@gmail.com/)** + +> iomap can return -ENOTBLK if pagecache invalidation fails. +> Let's make sure if -ENOTBLK is ever returned for atomic +> writes than we fail the write request (-EIO) instead of +> fallback to buffered-io. + +**[v5: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-fsdevel/cover.1729848252.git.lorenzo.stoakes@oracle.com/)** + +> This series introduces sentinels for this purposes which can be passed as +> the pidfd in this instance rather than having to establish a dummy fd for +> this purpose. + +**[v1: netfs: Add a check for NULL folioq in netfs_writeback_unlock_folios](http://lore.kernel.org/linux-fsdevel/ZxshMEW4U7MTgQYa@gmail.com/)** + +> syzkaller reported a null-pointer dereference bug +> (https://syzkaller.appspot.com/bug?extid=af5c06208fa71bf31b16) in +> netfs_writeback_unlock_folios caused by passing a NULL folioq to +> folioq_folio. Fix by adding a check before entering the loop. + +**[v1: ext4: Add atomic write support for DIO](http://lore.kernel.org/linux-fsdevel/cover.1729825985.git.ritesh.list@gmail.com/)** + +> This series adds the base feature support to enable atomic writes in +> direct-io path for ext4. We advertise the minimum and the maximum atomic +> write unit sizes via statx on a regular file. + +**[v1: virtio-fs: Query rootmode during mount](http://lore.kernel.org/linux-fsdevel/20241024164726.77485-1-hreitz@redhat.com/)** + +> During mount, receive the root inode's mode (e.g. whether it is a +> directory or a regular file) via GETATTR. + +**[v1: nilfs2: Finish folio conversion](http://lore.kernel.org/linux-fsdevel/20241024092602.13395-1-konishi.ryusuke@gmail.com/)** + +> This series converts all remaining page structure references in nilfs2 +> to folio-based, except for nilfs_copy_buffer function, which was +> converted to use folios in advance for cross-fs page flags cleanup. + +**[v2: sysctl: Reduce dput(child) calls in proc_sys_fill_cache()](http://lore.kernel.org/linux-fsdevel/582379a6-dea3-482f-86e4-259d4b23204e@web.de/)** + +**[v1: iomap: elide zero range flush from partial eof zeroing](http://lore.kernel.org/linux-fsdevel/20241023143029.11275-1-bfoster@redhat.com/)** + +> iomap zero range performs a pagecache flush upon seeing unwritten +> extents with dirty pagecache in order to determine accurate +> subranges that require direct zeroing. This is to support an +> optimization where clean, unwritten ranges are skipped as they are +> already zero on-disk. + +**[v1: mm/page-writeback: Raise wb_thresh to prevent write blocking with strictlimit](http://lore.kernel.org/linux-fsdevel/20241023100032.62952-1-jimzhao.ai@gmail.com/)** + +> With the strictlimit flag, wb_thresh acts as a hard limit in +> balance_dirty_pages() and wb_position_ratio(). + +#### 网络设备 + +**[v1: net-next: net: dlink: add get_ethtool_stats in ethtool](http://lore.kernel.org/netdev/20241026192651.22169-3-yyyynoom@gmail.com/)** + +> This patch implement `get_ethtool_stats` to support `ethtool -S`. + +**[v2: net-next: net: Use str_yes_no() helper function](http://lore.kernel.org/netdev/20241026152847.133885-3-thorsten.blum@linux.dev/)** + +> Remove hard-coded strings by using the str_yes_no() helper function. + +**[v2: net-next: Support some features for the HIBMCGE driver](http://lore.kernel.org/netdev/20241026115740.633503-1-shaojijie@huawei.com/)** + +> In this patch series, The HIBMCGE driver implements some functions +> such as statistics query, dump register, unicast MAC address filtering, +> debugfs and reset. + +**[v1: net-next: net: Use str_yes_no() and str_no_yes() helper functions](http://lore.kernel.org/netdev/20241026112946.129310-2-thorsten.blum@linux.dev/)** + +> Remove hard-coded strings by using the str_yes_no() and str_no_yes() +> helper functions. + +**[v1: bpf-next: net: tcp: replace the document for "lsndtime" in tcp_sock](http://lore.kernel.org/netdev/20241026065422.2820134-1-dongml2@chinatelecom.cn/)** + +> The document for "lsndtime" in struct tcp_sock is placed in the wrong +> place, so let's replace it in the proper place. + +**[v1: net-next: Side MDIO Support for LAN937x Switches](http://lore.kernel.org/netdev/20241026063538.2506143-1-o.rempel@pengutronix.de/)** + +> This patch set introduces support for an internal MDIO bus in LAN937x +> switches, enabling the use of a side MDIO channel for PHY management +> while keeping SPI as the main interface for switch configuration. + +**[v2: net-next: lib: packing: introduce and use (un)pack_fields](http://lore.kernel.org/netdev/20241025-packing-pack-fields-and-ice-implementation-v2-0-734776c88e40@intel.com/)** + +> This series improves the packing library with a new API for packing or +> unpacking a large number of fields at once with minimal code footprint. + +**[v1: Add LAN78XX OTP_ACCESS flag support](http://lore.kernel.org/netdev/20241025230550.25536-1-Fabi.Benschuh@fau.de/)** + +> With this flag we can now use ethtool to access the OTP: +> ethtool --set-priv-flags eth0 OTP_ACCESS on +> ethtool -e eth0 # this will read OTP if OTP_ACCESS is on, else EEPROM + +**[v3: net-next: eth: fbnic: Add support to write TCE TCAM entries](http://lore.kernel.org/netdev/20241025225910.30187-1-mohsin.bashr@gmail.com/)** + +> Add support for writing to the tce tcam to enable host to bmc traffic. + +**[v1: iproute: bridge: dump mcast querier state](http://lore.kernel.org/netdev/20241025142836.19946-1-f.pfitzner@pengutronix.de/)** + +> Kernel support for dumping the multicast querier state was added in this +> commit. + +**[v1: net-next: net: netpoll: Improve SKB pool management](http://lore.kernel.org/netdev/20241025142025.3558051-1-leitao@debian.org/)** + +> The netpoll subsystem pre-allocates 32 SKBs in a pool for emergency use +> during out-of-memory conditions. + +**[v10: net-next: Introducing OpenVPN Data Channel Offload](http://lore.kernel.org/netdev/20241025-b4-ovpn-v10-0-b87530777be7@openvpn.net/)** + +> Please note that patches previously reviewed by Andrew Lunn have +> retained the Reviewed-by tag as they have been simply rebased without +> major modifications. + +**[v1: net-next: tcp: only release congestion control if it has been initialized](http://lore.kernel.org/netdev/1729845944-6003-1-git-send-email-yangpc@wangsu.com/)** + +> In this case, tcp_cdg calls kfree(NULL) in release without causing +> an exception, but for some customized ca, this could lead to +> unexpected exceptions. + +**[v5: net-next: binder: report txn errors via generic netlink (genl)](http://lore.kernel.org/netdev/20241025075102.1785960-1-dualli@chromium.org/)** + +> It's a known issue that neither the frozen processes nor the system +> administration process of the OS can correctly deal with failed binder +> transactions. + +**[v1: net-next: net/smc: increase SMC_WR_BUF_CNT](http://lore.kernel.org/netdev/20241025074619.59864-1-wenjia@linux.ibm.com/)** + +> The current value of SMC_WR_BUF_CNT is 16 which leads to heavy +> contention on the wr_tx_wait workqueue of the SMC-R linkgroup and its +> spinlock when many connections are competing for the buffer. + +**[v8: Add NSS clock controller support for IPQ9574](http://lore.kernel.org/netdev/20241025035520.1841792-1-quic_mmanikan@quicinc.com/)** + +> Add bindings, driver and devicetree node for networking sub system clock +> controller on IPQ9574. Also add support for gpll0_out_aux clock +> which serves as the parent for some nss clocks. + +**[v4: rust: Add IO polling](http://lore.kernel.org/netdev/20241025033118.44452-1-fujita.tomonori@gmail.com/)** + +> polls periodically until a condition is met or a timeout is reached. +> By using the function, the 7th patch fixes QT2025 PHY driver to sleep +> until the hardware becomes ready. + +**[v2: next: uapi: socket: Introduce struct sockaddr_legacy](http://lore.kernel.org/netdev/23bd38a4bf024d4a92a8a634ddf4d5689cd3a67e.1729802213.git.gustavoars@kernel.org/)** + +> We are currently working on enabling the -Wflex-array-member-not-at-end +> compiler option. + +**[v1: net-next: r8169: add support for RTL8125D](http://lore.kernel.org/netdev/d0306912-e88e-4c25-8b5d-545ae8834c0c@gmail.com/)** + +> This adds support for new chip version RTL8125D, which can be found on +> boards like Gigabyte X870E AORUS ELITE WIFI7. Firmware rtl8125d-1.fw +> for this chip version is available in linux-firmware already. + +**[v2: net-next: socket: Print pf->create() when it does not clear sock->sk on failure.](http://lore.kernel.org/netdev/20241024201458.49412-1-kuniyu@amazon.com/)** + +> I suggested to put DEBUG_NET_WARN_ON_ONCE() in __sock_create() to +> catch possible use-after-free. + +#### 安全增强 + +**[v3: Add Nothing Phone (1) support](http://lore.kernel.org/linux-hardening/20241020205615.211256-1-danila@jiaxyga.com/)** + +> This series of patches adds support for the Nothing Phone (1), identified +> as nothing,spacewar. The Nothing Phone (1) is built on the Qualcomm +> Snapdragon 778G+ (SM7325-AE, also known as yupik). + +#### 异步 IO + +**[v1: Rewrite rsrc node handling](http://lore.kernel.org/io-uring/20241026222348.90331-1-axboe@kernel.dk/)** + +> This series handles the resource nodes separately, so a request pins +> just the resources it needs, and only for the duration of that request. + +**[v8: io_uring: support sqe group and leased group kbuf](http://lore.kernel.org/io-uring/20241025122247.3709133-1-ming.lei@redhat.com/)** + +> The 1st 3 patches are cleanup, and prepare for adding sqe group. +> +> The 4th patch supports generic sqe group which is like link chain, but +> allows each sqe in group to be issued in parallel and the group shares +> same IO_LINK & IO_DRAIN boundary, so N:M dependency can be supported with +> sqe group & io link together. +> +> The 5th & 6th patches supports to lease other subsystem's kbuf to +> io_uring for use in sqe group wide. +> +> The 7th patch supports ublk zero copy based on io_uring sqe group & +> leased kbuf. + +**[v1: Add support for provided registered buffers](http://lore.kernel.org/io-uring/20241023161522.1126423-1-axboe@kernel.dk/)** + +> This patchset adds support for using a mix of provided and registered +> buffers, where the provided buffers merely provide an index into which +> registered buffers to use. + +**[v1: implement vectored registered buffers for sendzc](http://lore.kernel.org/io-uring/cover.1729650350.git.asml.silence@gmail.com/)** + +> Allow registered buffers to be used with zerocopy sendmsg, where the +> passed iovec becomes a scatter list into the registered buffer +> specified by sqe->buf_index. See patches 3 and 4 for more details. + +**[v1: Add support for registered waits](http://lore.kernel.org/io-uring/20241022204708.1025470-1-axboe@kernel.dk/)** + +> While doing testing on zero-copy tx/rx with io_uring, I noticed that a +> LOT of time is being spent copying in data structures related to waiting +> on events. + +**[v4: btrfs: io_uring interface for encoded reads](http://lore.kernel.org/io-uring/20241022145024.1046883-1-maharmstone@fb.com/)** + +> This is version 4 of a patch series to add an io_uring interface for +> encoded reads. The principal use case for this is to eventually allow +> btrfs send and receive to operate asynchronously, the lack of io_uring +> encoded I/O being one of the main blockers for this. + +**[v1: send[msg] refactoring](http://lore.kernel.org/io-uring/cover.1729607201.git.asml.silence@gmail.com/)** + +> Clean up the send[msg] setup path. The pathes should be good enough by +> themselves, but more can be done on top. It's also needed as a +> dependency for supporting vectored fixed buffers for sendmsg zc. + +**[v1: Add support for ring resizing](http://lore.kernel.org/io-uring/20241022021159.820925-1-axboe@kernel.dk/)** + +> Something that's come up several times over the years is how to deal +> with ring sizing. + +#### Rust For Linux + +**[v1: Initial rust bindings for device property reads](http://lore.kernel.org/rust-for-linux/20241025-rust-platform-dev-v1-0-0df8dcf7c20b@kernel.org/)** + +> This series adds rust bindings for the device property API +> which is a firmware agnostic interface for reading firmware properties. + +**[v1: rust: list: make the cursor point between elements](http://lore.kernel.org/rust-for-linux/20241025-cursor-between-v1-1-08913714aae5@google.com/)** + +> The root cause of these +> signatures is that the cursor points *at* an element, rather than +> *between* two elements. + +**[v2: kbuild: simplify rustfmt target](http://lore.kernel.org/rust-for-linux/20241024170936.1922548-1-masahiroy@kernel.org/)** + +> There is no need to prune the rust/alloc directory because it was +> removed by commit 9d0441bab775 ("rust: alloc: remove our fork of the +> `alloc` crate"). + +**[v1: rust: platform: add Io support](http://lore.kernel.org/rust-for-linux/20241024-topic-panthor-rs-platform_io_support-v1-1-3d1addd96e30@collabora.com/)** + +> The IoMem is backed by ioremap_resource() + +**[v7: Extended MODVERSIONS Support](http://lore.kernel.org/rust-for-linux/20241023-extended-modversions-v7-0-339787b43373@google.com/)** + +> This patch series is intended for use alongside the Implement DWARF +> modversions series [1] to enable RUST and MODVERSIONS at the same +> time. + +**[v3: Device / Driver PCI / Platform Rust abstractions](http://lore.kernel.org/rust-for-linux/20241022213221.2383-1-dakr@kernel.org/)** + +> This patch series implements the necessary Rust abstractions to implement +> device drivers in Rust. + +**[v1: rust: miscdevice: add missing safety comments](http://lore.kernel.org/rust-for-linux/20241022-miscdevice-unsafe-warn-fix-v1-1-a78fde1740d6@google.com/)** + +> Note that these warnings are currently not enabled in the build, but +> rust-next contains a commit that will enable them, so we should fix +> them. + +#### BPF + +**[v3: PCI: add enabe(disable)_device() hook for bridge](http://lore.kernel.org/bpf/20241024-imx95_lut-v3-0-7509c9bbab86@nxp.com/)** + +> Add enable(disable)_device() hook for bridge can return error when not +> enough resource, and PCI device can't enabled. + +**[v3: tip/perf/core: SRCU-protected uretprobes hot path](http://lore.kernel.org/bpf/20241024044159.3156646-1-andrii@kernel.org/)** + +> This patch set adds return uprobe (uretprobe) side of this, this time +> utilizing SRCU for the same reasons. + +**[v1: bpf-next: net/smc: Introduce smc_bpf_ops](http://lore.kernel.org/bpf/1729737768-124596-1-git-send-email-alibuda@linux.alibaba.com/)** + +> This patches attempt to introduce BPF injection capability for SMC, +> and add selftest to ensure code stability. + +**[v3: bpf: Add the missing BPF_LINK_TYPE invocation for sockmap](http://lore.kernel.org/bpf/20241024013558.1135167-1-houtao@huaweicloud.com/)** + +> The tiny patch set fixes the out-of-bound read problem when reading the +> fdinfo of sock map link fd. + +**[v6: bpf-next: Share user memory to BPF program through task storage map](http://lore.kernel.org/bpf/20241023234759.860539-1-martin.lau@linux.dev/)** + +> It is the v6 of this series. Starting from v5, it is a continuation work +> of the RFC v4. + +**[v1: bpf: Extend the size of scratched_stack_slots to 128 bits](http://lore.kernel.org/bpf/20241023022752.172005-1-houtao@huaweicloud.com/)** + +> This additional stack +> space is reserved for spilling and filling of caller saved registers. + +**[v3: bpf: Preserve param->string when parsing mount options](http://lore.kernel.org/bpf/20241022130133.3798232-1-houtao@huaweicloud.com/)** + +> In bpf_parse_param(), keep the value of param->string intact so it can +> be freed later. + +**[v4: uprobes: Improve scalability by reducing the contention on siglock](http://lore.kernel.org/bpf/20241022073141.3291245-1-liaochang1@huawei.com/)** + +> The profiling result of BPF selftest on ARM64 platform reveals the +> significant contention on the current->sighand->siglock is the +> scalability bottleneck. + +**[v4: net-next: AccECN protocol preparation patch series](http://lore.kernel.org/bpf/20241021215910.59767-1-chia-yu.chang@nokia-bell-labs.com/)** + +> This updated patch series is grouped in preparation for the AccECN protocol, +> and is part of the full AccECN patch series. + +**[v1: bpf-next: bpf, x64: Introduce two tailcall enhancements](http://lore.kernel.org/bpf/20241021133929.67782-1-leon.hwang@linux.dev/)** + +> This patch set introduces two enhancements aimed at improving tailcall +> handling in the x64 JIT. + +### 周边技术动态 + +#### Qemu + +**[v7: tcg/riscv: Add support for vector](http://lore.kernel.org/qemu-devel/20241022001134.828724-1-richard.henderson@linaro.org/)** + +> Introduce support for the RISC-V vector extension in the TCG backend. + +#### U-Boot + +**[v2: PolarFire SoC clock devicetree rework](http://lore.kernel.org/u-boot/20241023101754.4021948-1-conor@kernel.org/)** + +> There's been no complaints about the only part that impacts U-Boot, +> so I figured it was time to send patches here. + +**[v1: riscv: mbv: Align DT with QEMU](http://lore.kernel.org/u-boot/077311f948de84c055ce2529370734b8ce310ad6.1729663597.git.michal.simek@amd.com/)** + +> Align U-Boot with QEMU amd-microblaze-v-virt platform to be able to wire +> it with CI. + +**[v1: CI: Add a test for building without CMDLINE](http://lore.kernel.org/u-boot/20241021134450.22985-1-sjg@chromium.org/)** + +> Something this breaks, so add a test to keep it working. Since sandbox +> enables a lot of options, it is a good board to use. + ## 20241020：第 114 期 -- Gitee