From 8e280100b737b07e4f0c087bf0f00de963eefda9 Mon Sep 17 00:00:00 2001 From: Rory Li <736729045@qq.com> Date: Sun, 13 Oct 2024 12:26:43 +0000 Subject: [PATCH] update news/README.md. Signed-off-by: Rory Li <736729045@qq.com> --- news/README.md | 758 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 758 insertions(+) diff --git a/news/README.md b/news/README.md index 7aaed93..ba7b909 100644 --- a/news/README.md +++ b/news/README.md @@ -8,6 +8,764 @@ * [2024 年 - 上半年](2024-1st-half.md) +## 20241013：第 113 期 + +### 内核动态 + +#### RISC-V 架构支持 + +**[v1: pinctrl: th1520: Unbreak the driver](http://lore.kernel.org/linux-riscv/20241011144826.381104-1-emil.renner.berthing@canonical.com/)** + +> Here are 2 important fixes and a code improvement to the T-Head TH1520 +> pinctrl driver that was either introduced or missed when Drew took over +> upstreaming it. + +**[v10: Add support for Allwinner PWM on D1/T113s/R329 SoCs](http://lore.kernel.org/linux-riscv/20241011102751.153248-1-privatesub2@gmail.com/)** + +**[v10: Tracepoints and static branch in Rust](http://lore.kernel.org/linux-riscv/20241011-tracepoint-v10-0-7fbde4d6b525@google.com/)** + +> This patch series +> adds support for calling tracepoints declared in C from Rust. +> This series includes a patch that adds a user of tracepoits to the +> rust_print sample. + +**[v3: ftrace: Consolidate ftrace_regs accessor functions for archs using pt_regs](http://lore.kernel.org/linux-riscv/20241010202114.2289f6fd@gandalf.local.home/)** + +> Most architectures use pt_regs within ftrace_regs making a lot of the +> accessor functions just calls to the pt_regs internally. + +> # s390 + +**[v9: Linux RISC-V IOMMU Support](http://lore.kernel.org/linux-riscv/cover.1728579958.git.tjeznach@rivosinc.com/)** + +> This patch series introduces support for RISC-V IOMMU architected +> hardware into the Linux kernel. + +**[v13: KVM: Stop grabbing references to PFNMAP'd pages](http://lore.kernel.org/linux-riscv/20241010182427.1434605-1-seanjc@google.com/)** + +> TL;DR: Eliminate KVM's long-standing (and heinous) behavior of essentially +> guessing which pfns are refcounted pages (see kvm_pfn_to_refcounted_page()). + +**[v5: Add board support for Sipeed LicheeRV Nano](http://lore.kernel.org/linux-riscv/20241010-sg2002-v5-0-a0f2e582b932@bootlin.com/)** + +> The LicheeRV Nano is a RISC-V SBC based on the Sophgo SG2002 chip. Adds +> minimal device tree files for this board to make it boot to a basic +> shell. + +**[v1: vdso: Preparations for generic data storage](http://lore.kernel.org/linux-riscv/20241010-vdso-generic-base-v1-0-b64f0842d512@linutronix.de/)** + +> These patches are intended to be merged via the tip tree, +> so the following patches can be based on a unified base. + +**[v2: riscv: interrupt-controller: Add T-HEAD C900 ACLINT SSWI](http://lore.kernel.org/linux-riscv/20241009224410.53188-1-inochiama@gmail.com/)** + +> Add full support for T-HEAD C900 SSWI device. + +**[v3: pinctrl: th1520: Improve code quality](http://lore.kernel.org/linux-riscv/20241008-th1520-pinctrl-fixes-v3-0-5b60db446a49@tenstorrent.com/)** + +> This series contains code quality improvements for the new TH1520 +> pinctrl driver. + +**[v2: ftrace: Make ftrace_regs abstract and consolidate code](http://lore.kernel.org/linux-riscv/20241008230527.674939311@goodmis.org/)** + +> I again compiled all the affected architectures (except for 32bit ppc). +> I got s390 built when disabling bcachefs. + +**[v6: riscv control-flow integrity for usermode](http://lore.kernel.org/linux-riscv/20241008-v5_user_cfi_series-v6-0-60d9fe073f37@rivosinc.com/)** + +> Software with larger attack surfaces (e.g. network facing apps like databases, +> browsers or apps relying on browser runtimes) suffer from memory corruption +> issues which can be utilized by attackers to bend control flow of the program +> to eventually gain control (by making their payload executable). + +**[v3: Introduce support for T-head TH1520 Mailbox](http://lore.kernel.org/linux-riscv/20241008174852.222374-1-m.wilczynski@samsung.com/)** + +> The T-head TH1520 SoC supports a hardware mailbox that enables two cores +> within the SoC to communicate and coordinate. + +**[v1: cfi: rust: pass -Zpatchable-function-entry on all architectures](http://lore.kernel.org/linux-riscv/20241008-cfi-patchable-all-v1-1-512481fd731d@google.com/)** + +> The KCFI sanitizer stores the CFI tag of a function just before its +> machine code. + +**[v2: mmc: sdhci-of-dwcmshc: Prevent stale command interrupt handling](http://lore.kernel.org/linux-riscv/20241008100327.4108895-1-m.wilczynski@samsung.com/)** + +> While working with the T-Head 1520 LicheePi4A SoC, certain conditions +> arose that allowed me to reproduce a race issue in the sdhci code. +> To solve this issue, we need to clear pending interrupts when resetting +> host->pending_reset. This ensures that after sdhci_threaded_irq restores +> interrupts, there are no pending stale interrupts. + +**[v3: pwm: Add pwm driver for Sophgo SG2042](http://lore.kernel.org/linux-riscv/cover.1728355974.git.unicorn_wang@outlook.com/)** + +> Add driver for pwm controller of Sophgo SG2042 SoC. + +**[v1: Add power key for pioneer box](http://lore.kernel.org/linux-riscv/cover.1728350655.git.unicorn_wang@outlook.com/)** + +> Add power key for pioneer box. + +**[v1: ftrace: Make ftrace_regs abstract from direct use](http://lore.kernel.org/linux-riscv/20241007204743.41314f1d@gandalf.local.home/)** + +> ftrace_regs was created to hold registers that store information to save +> function parameters, return value and stack. + +#### LoongArch 架构支持 + +**[v9: Consolidate IO memcpy functions](http://lore.kernel.org/loongarch/20241010123627.695191-1-jvetter@kalrayinc.com/)** + +> I have now guarded the prototypes as well with +> '#ifndef' and I have dropped the other unnecessary patches for now. + +**[v3: ASoC: Some issues about loongson i2s](http://lore.kernel.org/loongarch/cover.1728459624.git.zhoubinbin@loongson.cn/)** + +> This patch set is mainly about Loongson i2s related issues. + +#### ARM 架构支持 + +**[v6: Add mfd, pinctrl and pwm support to EN7581 SoC](http://lore.kernel.org/linux-arm-kernel/20241013-en7581-pinctrl-v6-0-2048e2d099c2@kernel.org/)** + +> Introduce airoha-mfd driver in order to load pinctrl and pwm drivers for +> EN7581 SoC. + +**[v1: ARM: mach-hpe: Rework support and directory structure](http://lore.kernel.org/linux-arm-kernel/20241011202638.806581-1-afd@ti.com/)** + +> Having a platform need a mach-* directory should be seen as a negative, +> it means the platform needs special non-standard handling. + +**[v6: Coresight: Add Coresight TMC Control Unit driver](http://lore.kernel.org/linux-arm-kernel/20241009112503.1851585-1-quic_jiegan@quicinc.com/)** + +> The significant challenge in enabling the data filter function is how +> to collect the trace ID of the source device. + +**[v5: RESEND: Coresight: Add Coresight TMC Control Unit driver](http://lore.kernel.org/linux-arm-kernel/20241009095556.1754876-1-quic_jiegan@quicinc.com/)** + +> The significant challenge in enabling the data filter function is how +> to collect the trace ID of the source device. + +**[v11: Introduction of a remoteproc tee to load signed firmware](http://lore.kernel.org/linux-arm-kernel/20241009080108.4170320-1-arnaud.pouliquen@foss.st.com/)** + +> To keep history of the updates I have kept in each patches the description +> of the updates versus the V9[2] revision. + +**[v7: Add NSS clock controller support for IPQ9574](http://lore.kernel.org/linux-arm-kernel/20241009074125.794997-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. + +**[v1: arm64: cpufeature: add POE to cpucap_is_possible()](http://lore.kernel.org/linux-arm-kernel/20241008140121.2774348-1-joey.gouly@arm.com/)** + +> Add CONFIG_ARM64_POE to cpucap_is_possible() to avoid the explicit check. + +#### X86 架构支持 + +**[v1: KVM: kvm-coco-queue: Support protected TSC](http://lore.kernel.org/lkml/cover.1728719037.git.isaku.yamahata@intel.com/)** + +> This patch series is for the kvm-coco-queue branch. + +**[v5: Dell AWCC platform_profile support](http://lore.kernel.org/lkml/20241012015849.19036-3-kuurtb@gmail.com/)** + +> This patch adds platform_profile support for Dell devices which implement +> User Selectable Thermal Tables (USTT) that are meant to be controlled by +> Alienware Command Center (AWCC). + +**[v5: Distinguish between variants of IBPB](http://lore.kernel.org/lkml/20241011214353.1625057-1-jmattson@google.com/)** + +> Prior to Zen4, AMD's IBPB did not flush the RAS (or, in Intel +> terminology, the RSB). + +**[v3: Improve objtool jump table handling](http://lore.kernel.org/lkml/20241011170847.334429-10-ardb+git@google.com/)** + +> Jump table handling has faded into the background a little due to the +> fact that jump tables are [currently] disabled when enabling retpoline +> mitigations and/or IBT on x86. + +**[v2: mm: Enforce the stack gap when changing inaccessible VMAs](http://lore.kernel.org/lkml/20241011-stack-gap-inaccessible-v2-1-111b6a0ee2cb@google.com/)** + +> As explained in the comment block this change adds, we can't tell what +> userspace's intent is when the stack grows towards an inaccessible VMA. + +**[v2: Add support for AMD hardware feedback interface](http://lore.kernel.org/lkml/20241010193705.10362-1-mario.limonciello@amd.com/)** + +> The AMD Heterogeneous core design and Hardware Feedback Interface (HFI) +> provide behavioral classification and a dynamically updated ranking table +> for the scheduler to use when choosing cores for tasks. + +**[v1: perf/amd/ibs: Add support for OP Load Latency Filtering](http://lore.kernel.org/lkml/20241010050815.751-1-ravi.bangoria@amd.com/)** + +> Add support for LdLat filtering in IBS Op pmu. Since hardware supports +> threshold in multiple of 128, add a software filter on top to support +> latency threshold with the granularity of 1 cycle between [128-2048]. + +**[v1: asus-laptop: prefer strscpy() over strcpy()](http://lore.kernel.org/lkml/20241009230558.51892-1-abdul.rahim@myyahoo.com/)** + +> The function strcpy() is depreciated and potentially unsafe. It performs +> no bounds checking on the destination buffer. + +#### 进程调度 + +**[v2: sched/eevdf: Reduce the computation frequency of avg_vruntime](http://lore.kernel.org/lkml/20241011062449.998696-1-xavier_qy@163.com/)** + +> The current code subtracts the value of curr from avg_vruntime and avg_load +> during runtime. Then, every time avg_vruntime() is called, it adds the +> value of curr to the avg_vruntime and avg_load. + +**[v1: sched/topology: improve topology_span_sane speed](http://lore.kernel.org/lkml/20241010155111.230674-1-steve.wahl@hpe.com/)** + +> Use a different approach to topology_span_sane(), that checks for the +> same constraint of no partial overlaps for any two CPU sets for +> non-NUMA topology levels, but does so in a way that is O(N) rather +> than O(N^2). + +**[v1: sched/core: Disable page allocation in task_tick_mm_cid()](http://lore.kernel.org/lkml/20241010014432.194742-1-longman@redhat.com/)** + +> With KASAN and PREEMPT_RT enabled, calling task_work_add() in +> task_tick_mm_cid() may cause the following splat. + +**[v3: sched+mm: Track lazy active mm existence with hazard pointers](http://lore.kernel.org/lkml/20241008135034.1982519-1-mathieu.desnoyers@efficios.com/)** + +> I'm posting a v3 taking care of feedback from Peter Zijlstra and Paul +> E. McKenney in case it can be useful to try hazard pointers with other +> use-cases, or for further benchmarking of active mm tracking impact. + +**[v1: sched: Lazy preemption muck](http://lore.kernel.org/lkml/20241007074609.447006177@infradead.org/)** + +> During LPC Thomas reminded me that the lazy preemption stuff was not there yet. + +#### 内存管理 + +**[v1: mm/hugetlb: Perform vmemmap optimization batchly for specific node allocation](http://lore.kernel.org/linux-mm/20241012070802.1876-1-suhua1@kingsoft.com/)** + +> When HVO is enabled and huge page memory allocs are made, the freed memory +> can be aggregated into higher order memory in the following paths, which +> facilitates further allocs for higher order memory. + +**[v1: Reduce dependence on vmas deep in hugetlb allocation code](http://lore.kernel.org/linux-mm/cover.1728684491.git.ackerleytng@google.com/)** + +> I hope to use these 3 patches to start a discussion on eventually +> removing the need to pass a struct vma pointer when taking a folio +> from the global pool (i.e. dequeue_hugetlb_folio_vma()). + +**[v2: vmscan: add a vmscan event for reclaim_pages](http://lore.kernel.org/linux-mm/20241011124928.1224813-1-jaewon31.kim@samsung.com/)** + +> The reclaim_folio_list uses a dummy reclaim_stat and is not being +> used. To know the memory stat, add a new trace event. This is useful how +> how many pages are not reclaimed or why. + +**[v1: mm/page_alloc: Let GFP_ATOMIC order-0 allocs access highatomic reserves](http://lore.kernel.org/linux-mm/20241011120737.3300370-1-matt@readmodwrite.com/)** + +> Under memory pressure it's possible for GFP_ATOMIC order-0 allocations +> to fail even though free pages are available in the highatomic reserves. +> GFP_ATOMIC allocations cannot trigger unreserve_highatomic_pageblock() +> since it's only run from reclaim. + +**[v2: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-mm/cover.1728643714.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: mm: make pcp decay work with onhz](http://lore.kernel.org/linux-mm/20241011103609.1992042-1-mengensun@tencent.com/)** + +> when a cpu stops tick, quiet_vmstat may flush all the per cpu +> statistics counter. + +**[v1: mm: don't install PMD mappings when THPs are disabled by the hw/process/vma](http://lore.kernel.org/linux-mm/20241011102445.934409-1-david@redhat.com/)** + +> During testing, it was found that we can get PMD mappings in processes +> where THP (and more precisely, PMD mappings) are supposed to be disabled. +> While it works as expected for anon+shmem, the pagecache is the problematic +> bit. + +**[v1: mm: Split BLK_FEAT_SYNCHRONOUS and SWP_SYNCHRONOUS_IO into separate read and write flags](http://lore.kernel.org/linux-mm/20241011091133.28173-1-qun-wei.lin@mediatek.com/)** + +> This patch splits the BLK_FEAT_SYNCHRONOUS feature flag into two +> separate flags: BLK_FEAT_READ_SYNCHRONOUS and +> BLK_FEAT_WRITE_SYNCHRONOUS. Similarly, the SWP_SYNCHRONOUS_IO flag is +> split into SWP_READ_SYNCHRONOUS_IO and SWP_WRITE_SYNCHRONOUS_IO. + +**[v1: mm/hugetlb: Concentrated releases memory when cmdline specifies node requests for large pages](http://lore.kernel.org/linux-mm/20241011080543.2422-1-suhua1@kingsoft.com/)** + +> This patch supports the release of huge page optimizations aggregates to +> higher order memory. + +**[v3: tmpfs: don't enable large folios if not supported](http://lore.kernel.org/linux-mm/20241011065919.2086827-1-wangkefeng.wang@huawei.com/)** + +> The tmpfs could support large folio, but there is some configurable +> options(mount options and runtime deny/force) to enable/disable large +> folio allocation, so there is a performance issue when perform write +> without large folio, the issue is similar to commit 4e527d5841e2 +> ("iomap: fault in smaller chunks for non-large folio mappings"). + +**[v1: RFC/RFT: Converge common flows for cpu assisted shadow stack](http://lore.kernel.org/linux-mm/20241010-shstk_converge-v1-0-631beca676e7@rivosinc.com/)** + +> x86, arm64 and risc-v support cpu assisted shadow stack. x86 was first +> one and most of the shadow stack related code is in x86 arch directory. +> arm64 guarded control stack (GCS) patches from Mark Brown are in -next. + +**[v3: tip/perf/core: uprobes,mm: speculative lockless VMA-to-uprobe lookup](http://lore.kernel.org/linux-mm/20241010205644.3831427-1-andrii@kernel.org/)** + +> Implement speculative (lockless) resolution of VMA to inode to uprobe, +> bypassing the need to take mmap_lock for reads, if possible. + +**[v6: tmpfs: Add case-insensitive support for tmpfs](http://lore.kernel.org/linux-mm/20241010-tonyk-tmpfs-v6-0-79f0ae02e4c8@igalia.com/)** + +> This patchset adds support for case-insensitive file names lookups in +> tmpfs. + +**[v1: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-mm/cover.1728578231.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. + +**[v4: vdso: Use only headers from the vdso/ namespace](http://lore.kernel.org/linux-mm/20241010135146.181175-1-vincenzo.frascino@arm.com/)** + +> The recent implementation of getrandom in the generic vdso library, +> includes headers from outside of the vdso/ namespace. + +**[v6: Rust support for mm_struct, vm_area_struct, and mmap for miscdevice](http://lore.kernel.org/linux-mm/20241010-vma-v6-0-d89039b6f573@google.com/)** + +> The first patch introduces mm_struct and vm_area_struct abstractions, +> and the second patch uses them for miscdevice. + +**[v1: mm: add pcp high_min high_max to proc zoneinfo](http://lore.kernel.org/linux-mm/20241010120935.656619-1-mengensun@tencent.com/)** + +> we output the pcp high_min/max to the zoneinfo + +**[v3: Support large folios for tmpfs](http://lore.kernel.org/linux-mm/cover.1728548374.git.baolin.wang@linux.alibaba.com/)** + +> This RFC patch series attempts to support large folios for tmpfs. +> Add a new huge option 'write_size' to support large folio allocation based +> on the write size for tmpfs write and fallocate paths. + +**[v3: KVM: Restricted mapping of guest_memfd at the host and arm64 support](http://lore.kernel.org/linux-mm/20241010085930.1546800-1-tabba@google.com/)** + +> This series adds restricted mmap() support to guest_memfd, as +> well as support for guest_memfd on arm64. It is based on Linux + +**[v3: mm/vmscan: stop the loop if enough pages have been page_out](http://lore.kernel.org/linux-mm/20241010081802.290893-1-chenridong@huaweicloud.com/)** + +> As shown above, the test_memcg used about 100M swap, but 600M+ swap memory +> was used, which means that 500M may be wasted because other memcgs can not +> use these swap memory. +> To fix this issue, it's better to stop looping if THP has been splited and +> nr_pageout is greater than nr_to_reclaim. + +**[v1: -v2: tdx, memory hotplug: Check whole hot-adding memory range for TDX](http://lore.kernel.org/linux-mm/20241010074726.1397820-1-ying.huang@intel.com/)** + +> On systems with TDX (Trust Domain eXtensions) enabled, memory ranges +> hot-added must be checked for compatibility by TDX. T + +**[v13: EDAC: Scrub: introduce generic EDAC RAS control feature driver + CXL/ACPI-RAS2 drivers](http://lore.kernel.org/linux-mm/20241009124120.1124-1-shiju.jose@huawei.com/)** + +> Previously known as "ras: scrub: introduce subsystem + CXL/ACPI-RAS2 drivers". + +**[v1: mm: throttle and inc min_seq when both page types reach MIN_NR_GENS](http://lore.kernel.org/linux-mm/20241009074953.608591-1-zhaoyang.huang@unisoc.com/)** + +> This commit solve the issue by have the reclaimer be throttled +> and increase min_seq if both page types reach MIN_NR_GENS, which may +> introduce a livelock of switching type with holding lruvec->lru_lock. + +**[v1: kaslr: rename physmem_end and PHYSMEM_END to direct_map_physmem_end](http://lore.kernel.org/linux-mm/20241009025024.89813-1-jhubbard@nvidia.com/)** + +> For clarity. It's increasingly hard to reason about the code, when KASLR +> is moving around the boundaries. + +**[答复: v1: Introduce panic function when slub leaks](http://lore.kernel.org/linux-mm/1728437107669.41520@unisoc.com/)** + +> For recording allocation information, I think CONFIG_MEM_ALLOC_PROFILING [1] [2] +> may be used to track allocation sites that contribute to memory leaks, +> instead of making the kernel panic or printing WARNING? + +#### 文件系统 + +**[v2: ovl: specify layers via file descriptors](http://lore.kernel.org/linux-fsdevel/20241011-work-overlayfs-v2-0-1b43328c5a31@kernel.org/)** + +> Currently overlayfs only allows specifying layers through path names. +> This is inconvenient for users such as systemd that want to assemble an +> overlayfs mount purely based on file descriptors. + +**[v1: fsnotify, lsm: Separate fsnotify_open_perm() and security_file_open()](http://lore.kernel.org/linux-fsdevel/20241011203722.3749850-1-song@kernel.org/)** + +> Currently, fsnotify_open_perm() is called from security_file_open(). This +> is not right for CONFIG_SECURITY=n and CONFIG_FSNOTIFY=y case, as +> security_file_open() in this combination will be a no-op and not call +> fsnotify_open_perm(). Fix this by calling fsnotify_open_perm() directly. + +**[v7: Hardware wrapped key support for QCom ICE and UFS core](http://lore.kernel.org/linux-fsdevel/20241011-wrapped-keys-v7-0-e3f7a752059b@linaro.org/)** + +> This series adds support for wrapped keys to the block layer, fscrypt +> and then build upwards from there by implementing relevant callbacks in +> QCom SCM driver, then the ICE driver and finally in UFS core and QCom +> layer. + +**[v20: Script execution control (was O_MAYEXEC)](http://lore.kernel.org/linux-fsdevel/20241011184422.977903-1-mic@digikod.net/)** + +> The ultimate goal of this patch series is to be able to ensure that +> direct file execution (e.g. ./script.sh) and indirect file execution +> (e.g. sh script.sh) lead to the same result, especially from a security +> point of view. + +**[v2: introduce PIDFD_SELF* sentinels](http://lore.kernel.org/linux-fsdevel/cover.1728643714.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. + +**[v4: API for exporting connectable file handles to userspace](http://lore.kernel.org/linux-fsdevel/20241011090023.655623-1-amir73il@gmail.com/)** + +> These patches bring the NFS connectable file handles feature to +> userspace servers. + +**[v11: pidfd: add ioctl to retrieve pid info](http://lore.kernel.org/linux-fsdevel/20241010155401.2268522-1-luca.boccassi@gmail.com/)** + +> A common pattern when using pid fds is having to get information +> about the process, which currently requires /proc being mounted, +> resolving the fd to a pid, and then do manual string parsing of +> /proc/N/status and friends. + +**[v1: coredump: add cond_resched() to dump_user_range](http://lore.kernel.org/linux-fsdevel/20241010113651.50cb0366@imladris.surriel.com/)** + +> Add a cond_resched() in dump_user_range() to avoid that softlockup. + +**[v3: extensible syscalls: CHECK_FIELDS to allow for easier feature detection](http://lore.kernel.org/linux-fsdevel/20241010-extensible-structs-check_fields-v3-0-d2833dfe6edd@cyphar.com/)** + +> This series adds CHECK_FIELDS support for the following extensible +> struct syscalls, as they are quite likely to grow flags in the near +> future. + +**[v1: fs: grab current_time() in setattr_copy_mgtime() when ATTR_CTIME is unset](http://lore.kernel.org/linux-fsdevel/20241009-mgtime-v1-1-383b9e0481b5@kernel.org/)** + +> With support of delegated timestamps, nfsd can issue a setattr that sets +> the atime, but not the ctime. Ensure that when the ctime isn't set that +> "now" is set to the current coarse-grained time. + +**[v10: pidfd: add ioctl to retrieve pid info](http://lore.kernel.org/linux-fsdevel/20241008132051.1011467-1-luca.boccassi@gmail.com/)** + +> A common pattern when using pid fds is having to get information +> about the process, which currently requires /proc being mounted, +> resolving the fd to a pid, and then do manual string parsing of +> /proc/N/status and friends. + +**[v1: fcntl: make F_DUPFD_QUERY associative](http://lore.kernel.org/linux-fsdevel/20241008-duften-formel-251f967602d5@brauner/)** + +> Currently when passing a closed file descriptor to +> fcntl(fd, F_DUPFD_QUERY, fd_dup) the order matters + +#### 网络设备 + +**[v1: net: phy: mdio-bcm-unimac: Add BCM6846 variant](http://lore.kernel.org/netdev/20241012-bcm6846-mdio-v1-0-c703ca83e962@linaro.org/)** + +> The BCM6846 has a few extra registers and cannot reuse the +> compatible string from other variants of the Unimac +> MDIO block: we need to be able to tell them apart. + +**[v4: net: octeon_ep: Add SKB allocation failures handling in __octep_oq_process_rx()](http://lore.kernel.org/netdev/20241012094950.9438-1-amishin@t-argos.ru/)** + +> In this series, we introduce two helpers to make the fix more readable and +> avoid code duplication. Also we handle build_skb() errors inside +> __octep_oq_process_rx() to avoid NULL pointer dereference. + +**[v2: net-next: net: airoha: Implement BQL support](http://lore.kernel.org/netdev/20241012-en7581-bql-v2-1-4deb4efdb60b@kernel.org/)** + +> Introduce BQL support in the airoha_eth driver reporting to the kernel +> info about tx hw DMA queues in order to avoid bufferbloat and keep the +> latency small. + +**[v1: net-next: eth: fbnic: Add devlink dev flash support](http://lore.kernel.org/netdev/20241012023646.3124717-1-lee@trager.us/)** + +> fbnic supports updating firmware using a PLDM image signed and distributed +> by Meta. PLDM images are written into stored flash. Flashing does not +> interrupt operation. + +**[v4: net-next: udp: Add 4-tuple hash for connected sockets](http://lore.kernel.org/netdev/20241012012918.70888-1-lulie@linux.alibaba.com/)** + +> This patchset introduces 4-tuple hash for connected udp sockets, to make +> connected udp lookup faster. + +**[v1: net-next: Threads support in proc connector](http://lore.kernel.org/netdev/20241012004532.2071738-1-anjali.k.kulkarni@oracle.com/)** + +> Recently we committed a fix to allow processes to receive notifications for +> non-zero exits via the process connector module. Commit is a4c9a56e6a2c. + +**[v6: net-next: eth: fbnic: Add hardware monitoring support via HWMON interface](http://lore.kernel.org/netdev/20241011235847.1209435-1-sanman.p211993@gmail.com/)** + +> This patch adds support for hardware monitoring to the fbnic driver, +> allowing for temperature and voltage sensor data to be exposed to +> userspace via the HWMON interface. + +**[v1: net-next: rtnetlink: Use rtnl_register_many().](http://lore.kernel.org/netdev/20241011220550.46040-1-kuniyu@amazon.com/)** + +> This series converts all rtnl_register() and rtnl_register_module() +> to rtnl_register_many() and finally removes them. + +**[v1: net: mtk_eth_soc: use ethtool_puts](http://lore.kernel.org/netdev/20241011200225.7403-1-rosenp@gmail.com/)** + +> Allows simplifying get_strings and avoids manual pointer manipulation. + +**[v1: net: mvneta: use ethtool_puts](http://lore.kernel.org/netdev/20241011195955.7065-1-rosenp@gmail.com/)** + +> Allows simplifying get_strings and avoids manual pointer manipulation. + +**[v1: net-next: lib: packing: introduce and use (un)pack_fields](http://lore.kernel.org/netdev/20241011-packing-pack-fields-and-ice-implementation-v1-0-d9b1f7500740@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: net-next: ethtool: rss: track rss ctx busy from core](http://lore.kernel.org/netdev/20241011183549.1581021-1-daniel.zahka@gmail.com/)** + +> This series prevents deletion of rss contexts that are +> in use by ntuple filters from ethtool core. + +**[v1: RESEND: net: sfp: change quirks for Alcatel Lucent G-010S-P](http://lore.kernel.org/netdev/TYCPR01MB84373677E45A7BFA5A28232C98792@TYCPR01MB8437.jpnprd01.prod.outlook.com/)** + +> Seems Alcatel Lucent G-010S-P also have the same problem that it uses +> TX_FAULT pin for SOC uart. So apply sfp_fixup_ignore_tx_fault to it. + +**[v1: net: genetlink: hold RCU in genlmsg_mcast()](http://lore.kernel.org/netdev/20241011171217.3166614-1-edumazet@google.com/)** + +> While running net selftests with CONFIG_PROVE_RCU_LIST=y I saw +> one lockdep splat . + +**[v1: net: macsec: don't increment counters for an unrelated SA](http://lore.kernel.org/netdev/f5ac92aaa5b89343232615f4c03f9f95042c6aa0.1728657709.git.sd@queasysnail.net/)** + +> On RX, we shouldn't be incrementing the stats for an arbitrary SA in +> case the actual SA hasn't been set up. + +**[v3: can: m_can: Add am62 wakeup support](http://lore.kernel.org/netdev/20241011-topic-mcan-wakeup-source-v6-12-v3-0-9752c714ad12@baylibre.com/)** + +> To support mcu_mcan0 and mcu_mcan1 wakeup for the mentioned SoCs, the +> series introduces a notion of wake-on-lan for m_can. + +**[v3: net-next: r8169: use the extended tally counter available from RTL8125](http://lore.kernel.org/netdev/a3b9d8d5-55e3-4881-ac47-aa98d1a86532@gmail.com/)** + +> The new hw stat fields partially duplicate existing fields, but with a +> larger field size now. Use these new fields to reduce the risk of +> overflows. In addition add support for relevant new fields which are +> available from RTL8125 only. + +**[v2: net: udp: Compute L4 checksum as usual when not segmenting the skb](http://lore.kernel.org/netdev/20241011-uso-swcsum-fixup-v2-1-6e1ddc199af9@cloudflare.com/)** + +> In the case when we are not taking the GSO path, but it has been requested, +> the software checksum fallback in skb_segment doesn't get a chance to +> compute the full checksum, if the egress device can't do it. + +**[v2: binder: report txn errors via generic netlink (genl)](http://lore.kernel.org/netdev/20241011064427.1565287-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. + +**[v2: net-next: net: phylink: allow half-duplex modes with RATE_MATCH_PAUSE](http://lore.kernel.org/netdev/b157c0c289cfba024039a96e635d037f9d946745.1728617993.git.daniel@makrotopia.org/)** + +> PHYs performing rate-matching using MAC-side flow-control always +> perform duplex-matching as well in case they are supporting +> half-duplex modes at all. + +**[v1: net: enetc: add missing static descriptor and inline keyword](http://lore.kernel.org/netdev/20241011030103.392362-1-wei.fang@nxp.com/)** + +> Fix the build warnings when CONFIG_FSL_ENETC_MDIO is not enabled. +> The detailed warnings are shown as follows. + +**[v1: net-next: net: bcmasp: enable SW timestamping](http://lore.kernel.org/netdev/20241010221506.802730-1-justin.chen@broadcom.com/)** + +> Add skb_tx_timestamp() call and enable support for SW +> timestamping. + +**[v1: of: net: Add option for random mac address](http://lore.kernel.org/netdev/20241010215417.332801-1-igilca1980@gmail.com/)** + +> Embedded devices that don't have a fixed mac address may want +> to use this property. For example dsa switch ports may use this property in +> order avoid setting this from user space. + +**[v2: User random address if dt sets so](http://lore.kernel.org/netdev/20241010202949.226488-1-igilca1980@gmail.com/)** + +**[v2: net: atlantic: support reading SFP module info](http://lore.kernel.org/netdev/20241010190617.391638-1-lorenz@brun.one/)** + +> Add support for reading SFP module info and digital diagnostic +> monitoring data if supported by the module. + +**[v3: net-next: tcp: add skb->sk to more control packets](http://lore.kernel.org/netdev/20241010174817.1543642-1-edumazet@google.com/)** + +> Currently, TCP can set skb->sk for a variety of transmit packets. + +**[v1: net-next: net: ethernet: ti: am65-cpsw: Enable USXGMII mode for J7200 CPSW5G](http://lore.kernel.org/netdev/20241010150543.2620448-1-s-vadapalli@ti.com/)** + +> TI's J7200 SoC supports USXGMII mode. Add USXGMII mode to the +> extra_modes member of the J7200 SoC data. + +#### 安全增强 + +**[v2: x86/stackprotector: Work around strict Clang TLS symbol requirements](http://lore.kernel.org/linux-hardening/20241009124352.3105119-2-ardb+git@google.com/)** + +> GCC and Clang both implement stack protector support based on Thread +> Local Storage (TLS) variables, and this is used in the kernel to +> implement per-task stack cookies, by copying a task's stack cookie into +> a per-CPU variable every time it is scheduled in. + +#### 异步 IO + +**[v7: io_uring: support sqe group and leased group kbuf](http://lore.kernel.org/io-uring/20241012085330.2540955-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: io_uring zero copy rx](http://lore.kernel.org/io-uring/20241007221603.1703699-1-dw@davidwei.uk/)** + +> This patchset adds support for zero copy rx into userspace pages using +> io_uring, eliminating a kernel to user copy. + +**[v1: io_uring/rw: allow non-blocking attempts for !FMODE_NOWAIT if pollable](http://lore.kernel.org/io-uring/ce905994-79d2-4783-9f49-9277238a9b30@kernel.dk/)** + +> The checking for whether or not io_uring can do a non-blocking read or +> write attempt is gated on FMODE_NOWAIT. + +#### Rust For Linux + +**[v2: rust: transmute: Add implementation for FromBytes trait](http://lore.kernel.org/rust-for-linux/20241012070121.110481-1-christiansantoslima21@gmail.com/)** + +> Add implementation and documentation for FromBytes trait. + +**[v1: 6.1.y: rust: macros: provide correct provenance when constructing THIS_MODULE](http://lore.kernel.org/rust-for-linux/20241011231228.4070521-1-boqun.feng@gmail.com/)** + +> commit a5a3c952e82c1ada12bf8c55b73af26f1a454bd2 upstream. + +**[v1: Character device abstractions for Rust](http://lore.kernel.org/rust-for-linux/20241011-rust-char-dev-v1-0-350225ae228b@walterzollerpiano.com/)** + +> Writing character devices is a common way to start writing kernel code, +> especially because of the book "Linux Device Drivers", which is still +> one of the best resources to learn about Linux kernel programming. + +**[v5: rust: query the compiler for dylib path](http://lore.kernel.org/rust-for-linux/20241010142833.98528-2-tamird@gmail.com/)** + +> Rust proc-macro crates are loaded by the compiler at compile-time, so +> are always dynamic libraries; on macOS, these artifacts get a .dylib +> extension rather than .so. + +**[v1: rust: improve grammar in commentary](http://lore.kernel.org/rust-for-linux/20241009162358.27735-1-tamird@gmail.com/)** + +> Commit e26fa546042a ("rust: kbuild: auto generate helper exports") +> added an errant "the" where one was not needed; remove it. + +**[v1: rust: LED abstractions](http://lore.kernel.org/rust-for-linux/20241009105759.579579-1-me@kloenk.dev/)** + +> This RFC implements a basic LED abstraction to show how this would work with rust. + +**[v4: Implement DWARF modversions](http://lore.kernel.org/rust-for-linux/20241008183823.36676-21-samitolvanen@google.com/)** + +> Here's v4 of the DWARF modversions series. The main motivation is +> modversions support for Rust, which is important for distributions +> like Android that are about to ship Rust kernel modules. Per Luis' +> request [1], v2 dropped the Rust specific bits from the series and +> instead added the feature as an option for the entire kernel. + +**[v1: scripts: add `uapi` crate to `generate_rust_analyzer.py`](http://lore.kernel.org/rust-for-linux/20241006225952.45012-1-luna.xin.lx@gmail.com/)** + +> This patch updates the `generate_rust_analyzer.py` script to include +> the `uapi` crate. + +**[v4: rust: optimize error type to use nonzero](http://lore.kernel.org/rust-for-linux/BL0PR02MB4914B9B088865CF237731207E9732@BL0PR02MB4914.namprd02.prod.outlook.com/)** + +> This reduces the space used by the `Result` type, as the `NonZero*` +> type enables the compiler to apply more efficient memory layout. + +**[v2: net-next: rust: Add IO polling](http://lore.kernel.org/rust-for-linux/20241005122531.20298-1-fujita.tomonori@gmail.com/)** + +> Add Rust version of read_poll_timeout (include/linux/iopoll.h), which +> polls periodically until a condition is met or a timeout is reached. + +#### BPF + +**[v2: net-next: net-timestamp: bpf extension to equip applications transparently](http://lore.kernel.org/bpf/20241012040651.95616-1-kerneljasonxing@gmail.com/)** + +> A few weeks ago, I planned to extend SO_TIMESTMAMPING feature by using +> tracepoint to print information (say, tstamp) so that we can +> transparently equip applications with this feature and require no +> modification in user side. + +**[v4: -next: perf stat: Support inherit events for bperf](http://lore.kernel.org/bpf/20241012023225.151084-1-wutengda@huaweicloud.com/)** + +> Here is the 4th version of the series to support inherit events for bperf. +> This version adds an `inherit` flag to bperf to control inherit behavior. + +**[v8: iwl-next: igb: Add support for AF_XDP zero-copy](http://lore.kernel.org/bpf/20241011-b4-igb_zero_copy-v8-0-83862f726a9e@linutronix.de/)** + +> This is version v8 of the AF_XDP zero-copy support for igb. Since Sriram's +> duties changed I am sending this instead. Additionally, I've tested this on +> real hardware, Intel i210 . + +**[v5: bpf-next: bpf: Add kmem_cache iterator and kfunc](http://lore.kernel.org/bpf/20241010232505.1339892-1-namhyung@kernel.org/)** + +> I'm proposing a new iterator and a kfunc for the slab memory allocator +> to get information of each kmem_cache like in /proc/slabinfo or +> /sys/kernel/slab in more flexible way. + +**[v4: bpf-next: bpf: Support private stack for bpf progs](http://lore.kernel.org/bpf/20241010175552.1895980-1-yonghong.song@linux.dev/)** + +> The main motivation for private stack comes from nested scheduler in +> sched-ext from Tejun. + +**[v1: net-next: net/smc: Introduce a hook to modify syn_smc at runtime](http://lore.kernel.org/bpf/1728532691-20044-1-git-send-email-alibuda@linux.alibaba.com/)** + +> The introduction of IPPROTO_SMC enables eBPF programs to determine +> whether to use SMC based on the context of socket creation, such as +> network namespaces, PID and comm name, etc. + +**[v4: tracing: Allow system call tracepoints to handle page faults](http://lore.kernel.org/bpf/20241009010718.2050182-1-mathieu.desnoyers@efficios.com/)** + +> This series does the initial wire-up allowing tracers to handle page +> faults, but leaves out the actual handling of said page faults as future +> work. + +**[v1: bpf: use kvzmalloc to allocate BPF verifier environment](http://lore.kernel.org/bpf/20241008170735.16766766@imladris.surriel.com/)** + +> The kzmalloc call in bpf_check can fail when memory is very fragmented, +> which in turn can lead to an OOM kill. + +### 周边技术动态 + +#### Qemu + +**[v1: riscv: AIA userspace irqchip_split support](http://lore.kernel.org/qemu-devel/20241010190337.376987-1-dbarboza@ventanamicro.com/)** + +> This series adds AIA irqchip_split support, effective when using AIA +> with aia=aplic-imsic and -accel kvm,kernel-irqchip=split. + +**[v16: riscv support for control flow integrity extensions](http://lore.kernel.org/qemu-devel/20241008225010.1861630-1-debug@rivosinc.com/)** + +> v16 for riscv zicfilp and zicfiss extensions support in qemu. + +**[v6: qemu: target/riscv: Add Zilsd and Zclsd extension support](http://lore.kernel.org/qemu-devel/172835886767.17327.15494840848441210001-0@git.sr.ht/)** + +> This patch adds support for the Zilsd and Zclsd extension, +> which is documented at https://github.com/riscv/riscv-zilsd/releases/tag/v0.10 + +**[v1: target/riscv: Support SXL32 on RV64 CPU](http://lore.kernel.org/qemu-devel/20241007033400.50163-1-zhiwei_liu@linux.alibaba.com/)** + +> We have implemented UXL32 on QEMU already. It enables us to run RV32 +> applications on RV64 Linux on QEMU. + +**[v5: tcg/riscv: Add support for vector](http://lore.kernel.org/qemu-devel/20241007025700.47259-1-zhiwei_liu@linux.alibaba.com/)** + +> This patch set introduces support for the RISC-V vector extension +> in TCG backend for RISC-V targets. + +#### U-Boot + +**[v5: Add Starfive JH7110 Cadence USB driver](http://lore.kernel.org/u-boot/20241012031328.4268-1-minda.chen@starfivetech.com/)** + +> Add Starfive JH7110 Cadence USB driver and related PHY driver. +> So the codes can be used in visionfive2 and star64 7110 board. + + ## 20241006：第 112 期 ### 内核动态 -- Gitee