# patches Software patches are changes or components applied to software to correct security or functionality problems, repair programming issues, or add capabilities. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cisco drops another exploited zero-day, this time a perfect 10 DevFeed: [Cisco drops another exploited zero-day, this time a perfect 10]() Original publisher: [Read original article]() Author: Carly Page Published: 2026-09-17T12:40:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Cisco](), [Authentication](), [Security](), [patches]() Tags: [authentication-bypass](), [cisco](), [cybersecurity](), [security](), [zero-day]() ### AI overview Cisco's ISE authentication bypass is under active attack, following another Cisco zero-day that prompted administrators to urgently apply patches. ### Source excerpt ISE authentication bypass under active attack just days after another Cisco zero-day sent admins scrambling to patch ## Libreboot 20231106 released! DevFeed: [Libreboot 20231106 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [boot](), [coreboot](), [bug](), [patches](), [Hardware](), [x86]() Tags: [bios](), [bug](), [bug-fixes](), [canoeboot](), [coreboot](), [firmware](), [free-software](), [grub](), [hardware](), [libre](), [libreboot](), [opensource](), [release](), [uefi](), [x86]() ### AI overview Libreboot 20231106 is a testing release focused on minor bug fixes and GRUB payload changes. It resolves boot issues affecting GM45 ThinkPads and adjusts the DDR2 RAM initialization patch for the Dell Latitude E6400 so it no longer affects other GM45 machines using DDR3 memory. ### Source excerpt Article: Libreboot 20231106 released! Web link: https://libreboot.org/news/libreboot20231106.html ## Libreboot 20140711 release DevFeed: [Libreboot 20140711 release]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [Graphics](), [patches](), [Documentation]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [firmware](), [free-software](), [libre](), [libreboot](), [opensource](), [patches](), [release](), [uefi]() ### AI overview The Libreboot 20140711 beta release updates its coreboot base, removes blobs, adds support for the T60 and MacBook2,1, introduces native graphics for supported laptops, and includes build, documentation, backlight, LCD-panel, and 3D-fix changes. ### Source excerpt Article: Libreboot 20140711 release Web link: https://libreboot.org/news/libreboot20140711.html ## GM45 no-microcode bug mitigations re-added (ThinkPad X200, T400 etc) DevFeed: [GM45 no-microcode bug mitigations re-added (ThinkPad X200, T400 etc)]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [bug](), [patches](), [Hardware](), [x86]() Tags: [bios](), [bug](), [canoeboot](), [coreboot](), [free-software](), [hardware](), [libre](), [libreboot](), [opensource](), [patches](), [uefi](), [x86]() ### AI overview Libreboot restored mitigations for a broken SpeedStep/reboot issue on GM45 hardware, including ThinkPad X200 and T400 systems. The article explains the relationship between these mitigations and Libreboot's default CPU microcode policy, and notes that the change was included in Libreboot 20230423 for all GM45 targets. ### Source excerpt Article: GM45 no-microcode bug mitigations re-added (ThinkPad X200, T400 etc) Web link: https://libreboot.org/news/gm45microcode.html ## Mesa 26.2.3 Released With AMD GFX1171 Support, Other Fixes DevFeed: [Mesa 26.2.3 Released With AMD GFX1171 Support, Other Fixes]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T21:18:50Z Content type: news Language: en Sources: [Phoronix]() Topics: [GPU](), [patches](), [Adreno](), [intel](), [Qualcomm](), [Firefox](), [Memory Leaks](), [Flight]() Tags: [adreno](), [amd](), [browser](), [bug](), [bug-fixes](), [desktop-linux](), [firefox](), [gpu](), [intel](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [memory-leak](), [open-source-graphics](), [patches](), [phoronix](), [phoronix-test-suite](), [qualcomm](), [release](), [stable](), [ubuntu-benchmarks](), [ubuntu-hardware](), [vulkan]() ### AI overview Mesa 26.2.3 is a stable bi-weekly point release containing backported bug fixes for RadeonSI, RADV, Freedreno, Turnip, Intel ANV, Asahi, NVK, and other drivers. It also adds AMD GFX1171 support. ### Source excerpt Mesa 26.2.3 is out today as the newest stable point release in this quarter's Mesa 26.2 series... ## n8n Patches 16 Security Vulnerabilities, 12 Rated High Severity DevFeed: [n8n Patches 16 Security Vulnerabilities, 12 Rated High Severity]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-16T18:31:20Z Content type: news Language: en Sources: [Self Host Lab]() Topics: [n8n](), [Vulnerabilities](), [patches](), [Security](), [Self-hosted]() Tags: [automation](), [n8n](), [news](), [patches](), [security](), [security-vulnerabilities](), [self-hosted](), [update](), [vulnerabilities]() ### AI overview n8n published a bi-weekly security update disclosing 16 fixed advisories: 12 rated High severity and 4 rated Medium. The article highlights an unauthenticated NoSQL injection in the MongoDB Chat Memory node that can disclose chat history across sessions, along with five High-severity credential-handling advisories. ### Source excerpt n8n, the self-hosted workflow automation platform covered regularly on this site, published its bi-weekly security update on September 16, 2026. The bulletin, posted on the official n8n Community forum by a member of the n8n security team, discloses 16 advisories fixed since the previous update on September 2: 12 rated High severity and 4 rated [...] ## Linux's Yogafan Driver Prepares Support For Newer Lenovo Laptops DevFeed: [Linux's Yogafan Driver Prepares Support For Newer Lenovo Laptops]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T10:29:22Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Kernel](), [Monitoring](), [patches](), [Open Source]() Tags: [desktop-linux](), [driver](), [kernel](), [laptops](), [lenovo](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [monitoring](), [open-source](), [open-source-graphics](), [patches](), [phoronix](), [phoronix-test-suite](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview The Yogafan HWMON driver is gaining support for several newer Lenovo laptops in the upcoming Linux 7.4 kernel cycle. Patches queued in the hwmon-next branch add fan speed monitoring support for the Lenovo Yoga Pro 9 16IMH9, Yoga 740-15IML, IdeaPad 3 15ALC6 Ub, and Yoga 14cACN 2021. ### Source excerpt Introduced back in Linux 7.1 was the Yogafan HWMON driver for supporting fan speed monitoring across various Lenovo Yoga, Legion, Flex, Slim, and IdeaPad laptops. An initial set of Lenovo laptops was initially supported by this driver while succeeding kernel versions have continued building out the support... ## Technical debt reduction and improved scanning could make software safer sooner DevFeed: [Technical debt reduction and improved scanning could make software safer sooner]() Original publisher: [Read original article]() Author: Simon Sharwood Published: 2026-09-16T05:54:47Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Software](), [patches](), [Development]() Tags: [ai-and-ml](), [mythos](), [patch-management](), [patches](), [security](), [software](), [technical]() ### AI overview The article discusses how paying down technical debt and improving software scanning could make software safer sooner, potentially easing patching challenges in 2027. ### Source excerpt Gartner sees huge amounts of technical debt paid down, and better scanning that could make software safer sooner ## Linux 7.4 slated to merge AVX-512 optimization for xor\_gen() DevFeed: [Linux 7.4 slated to merge AVX-512 optimization for xor\_gen()]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T00:53:15Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Kernel](), [patches](), [Code](), [cpu](), [intel](), [Google]() Tags: [amd](), [cpu](), [desktop-linux](), [google](), [intel](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-kernel](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [patches](), [phoronix](), [phoronix-test-suite](), [server-cpus](), [ubuntu-benchmarks](), [ubuntu-hardware](), [xor]() ### AI overview Linux 7.4 is slated to merge an AVX-512 optimization for xor_gen(), a function used by Linux software RAID to generate and validate parity blocks for RAID5 and RAID6. The patches report performance gains on AMD Zen 4 and newer CPUs and current Intel server CPUs with AVX-512, subject to final merge-window changes. ### Source excerpt Over the past few months there have been patches floating around for an AVX-512 optimized xor_gen() for the Linux kernel for that functuon used by the Linux software RAID code. It's been shhowing very nice performance gains with this function being used for generating and validating parity blocks such as for RAID5 and RAID6. The upcoming Linux 7.4 cycle is slated to merge this nice enhancement for benefiting AMD Zen 4 and newer or current Intel server CPUs with AVX-512... ## \[$\] PostgreSQL 19's "scary patch contest" DevFeed: [\[$\] PostgreSQL 19's "scary patch contest"]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-10T17:29:06Z Content type: news Language: en Sources: [LWN.net]() Topics: [PostgreSQL](), [patches](), [Testing](), [bug]() Tags: [beta](), [bug](), [patches](), [postgresql](), [release](), [stable](), [testing]() ### AI overview The PostgreSQL 19 release faced concerns about the readiness of several patches after unusually many bug fixes and ongoing revisions. One patch was reverted, and an extra beta release was scheduled for additional testing. ### Source excerpt PostgreSQL 19 was expected to be released in September, in keeping with the database project's longstanding tradition of a major release every year. However, some late-breaking concerns about several of the features slated for inclusion has some developers worried about the quality of the release. On August 25, PostgreSQL contributor Robert Haas sent an email with the subject "scary patch contest" about several patches that have required an unusually large number of bug fixes leading up to the release, which has raised questions about their readiness for a stable release. One of the patches has been reverted, but several are still under heavy revision, and an extra beta release has been slotted in to allow for additional testing. ## How AI agents could shift software work from code changes to specifications and module rebuilds DevFeed: [How AI agents could shift software work from code changes to specifications and module rebuilds]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-05-04T16:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Artificial Intelligence](), [Software Engineering](), [Agent Skills](), [Software](), [Refactoring](), [modules](), [patches]() Tags: [agents](), [ai](), [code](), [module](), [patches](), [refactoring](), [software-engineering]() ### AI overview This opinion article argues that AI agents may act like compilers, turning detailed specifications into software and reducing the need to write implementation code directly. Drawing on examples where the author changed implementations while preserving behavior, it suggests that agents could make rebuilding entire modules more practical than incremental patching and refactoring. ### Source excerpt Linus Torvalds recently said1 AI will be to code what compilers were to assembly -- freeing us from writing it by hand. Around the same time, I talked with Jesse Vincent (creator of one of the most popular agent skills out there -- superpowers). Something he said stuck with me: Specs are going to be the new code. I realize those two ideas snap together a little too neatly. Agents are compilers2 and specs will become code. Software engineering is moving up another level of abstraction and we've seen this play out before. Specs as source ## I saw this first-hand with my tiny USB-C cable checker -- usbi. It started as a shell command over macOS's system_profiler, then became Go when I wanted a proper binary, then Rust because I wanted to practice Rust, and later a .kts version. The code kept changing. The thing I cared about did not: parse the USB tree, identify the attached devices, report the speed, and make bad cables obvious. Podsync, my voice track sync program, followed the same pattern. It started in Python because the audio libraries were there. Then I moved it to Rust because I didn't want to ship a Python runtime or care which Python version happened to be on a machine. Again, the implementation changed. The behavior stayed boringly stable: take a master track and local tracks, find the offset, pad or trim each file, and drop aligned audio into the DAW. Compilers freed us from writing assembly. Agents may free us from writing code because it becomes an artifact the spec produces. The somewhat recent push around detailed exec plans could be an early signal of the looming shift at bigger scale. Rebuilds instead of patches ## Push that thought further. We might get comfortable rebuilding whole modules instead of patching and refactoring them. We preserved the old shape of a system because throwing it away cost too much. Even when you know the module is wrong, you sand it down: extract an interface, migrate one caller at a time, add tests around behavior nobody full ## Go 1.26.2: Security Fixes, Regression Patches, Upgrade Playbook DevFeed: [Go 1.26.2: Security Fixes, Regression Patches, Upgrade Playbook]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2026-04-09T00:00:00Z Content type: release Language: en Sources: [Ratn Labs]() Topics: [Go Language](), [upgrade](), [patches](), [Security]() Tags: [backend](), [beginner](), [go](), [go-security-backend-release-engineering](), [golang](), [patches](), [release-engineering](), [security](), [technical](), [upgrade]() ### AI overview This article covers the Go 1.26.2 release, including its security fixes and regression patches, and provides guidance for upgrading safely in production. ### Source excerpt A beginner-friendly and technical deep dive into Go 1.26.2: what changed, why it matters, and how to upgrade safely in production. ## Announcing GA for Worker Versioning and Public Preview for Upgrade on Continue-as-New DevFeed: [Announcing GA for Worker Versioning and Public Preview for Upgrade on Continue-as-New]() Original publisher: [Read original article]() Author: Brandon Chavis Published: 2026-03-30T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [version](), [Deployment](), [patches](), [configuration](), [upgrade]() Tags: [deployment](), [long-running](), [patches](), [preview](), [product-news](), [upgrade](), [versioning](), [workflow]() ### AI overview Temporal announces General Availability for Worker Versioning and a Public Preview of Upgrade on Continue-as-New. The article explains how versioning can replace workflow patches and how long-running Workflows can upgrade at Continue-as-New boundaries. ### Source excerpt Today, we're announcing the General Availability of Worker Versioning and a Public Preview of Upgrade on Continue-as-New, a new capability that eliminates patching for many long-running Workflow patterns. ## The 64-bit Hurd is Here! DevFeed: [The 64-bit Hurd is Here!]() Original publisher: [Read original article]() Author: Janneke Nieuwenhuizen, Yelninei Published: 2026-03-01T10:00:00Z Content type: article Language: en Sources: [GNU Guix -- Blog]() Topics: [x86](), [bug](), [patches](), [gcc]() Tags: [bug](), [gcc](), [gnu-hurd](), [patches](), [x86](), [x86-64]() ### AI overview Guix has added x86_64 support for the Hurd. The article reviews roughly 1.5 years of related work, including installer support, build and dependency fixes, package updates, and the merge of the 64-bit Hurd changes. ### Source excerpt Fifteen months have passed since our last Guix/Hurd on a Thinkpad X60 post and a lot has happened with respect to the Hurd . And most of you will have guessed, unless you skipped the title of this post, the rumored x86_64 support has landed in Guix! Here is a not-so-short overview of our Hurd work over the past 1.5 years: The build daemon fails when invoking guix authenticate on the Hurd bug was fixed. This was our most pressing problem as it meant that we could not keep... ## Deploying Keycloak on CockroachDB with Phase Two: A Complete Guide DevFeed: [Deploying Keycloak on CockroachDB with Phase Two: A Complete Guide]() Original publisher: [Read original article]() Author: Amine El Kouhen, Ph.D. Published: 2026-01-14T00:00:00Z Content type: tutorial Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Software as a service](), [Databases](), [Authentication](), [Authorization](), [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [consistency](), [Open Source](), [backups](), [patches](), [Entra ID]() Tags: [access-control](), [authentication](), [authorization](), [availability](), [backups](), [cockroachdb](), [consistency](), [databases](), [distributed](), [guide](), [high-availability](), [iam](), [identity-and-access-management](), [keycloak](), [oidc](), [openid-connect](), [patches](), [saas](), [saml](), [security]() ### AI overview This guide explains how Phase Two's managed Keycloak platform can be deployed with CockroachDB to support authentication, authorization, enterprise SSO, and multi-tenant SaaS applications. It describes Keycloak's identity-management capabilities and CockroachDB's globally distributed SQL database, transactional consistency, and tenant isolation. ### Source excerpt Today's SaaS products face twin demands: the digital identity layer must be seamless and enterprise-grade, and the data layer must scale globally while remaining reliably consistent. ## 2025年总结 DevFeed: [2025年总结]() Original publisher: [Read original article]() Published: 2025-12-31T08:00:00Z Content type: article Language: zh Sources: [MaskRay]() Topics: [toolchain](), [LLVM](), [patches](), [Linux]() Tags: [assembler](), [blogging](), [bugs](), [https-maskray-me-blog-tags-assembler](), [linux](), [llvm](), [patches](), [summary]() ### AI overview A 2025 personal summary covering reduced open-source involvement, 18 blog posts, work on LLVM's integrated assembler and ELF specifications, Linux kernel contributions, ccls, binutils reports, and travel. ### Source excerpt TODO 一如既往，主要在工具链领域耕耘。但由于工作忙碌在open source社区投入的时间减少了。 Blogging 不包括这篇总结，一共写了18篇文章。 ## lld 21 ELF changes DevFeed: [lld 21 ELF changes]() Original publisher: [Read original article]() Published: 2025-09-07T07:00:00Z Content type: release Language: en Sources: [MaskRay]() Topics: [LLVM](), [patches](), [toolchain](), [Arm](), [RISC-V](), [TLS (Transport Layer Security)]() Tags: [architecture](), [arm](), [linker](), [llvm](), [optimization](), [patches](), [release](), [riscv](), [tls]() ### AI overview An overview of selected changes in the ELF linker lld included with LLVM 21.1, covering symbol handling, garbage-collection diagnostics, ThinLTO, linker scripts, architecture-specific features, branch relaxation, TLS optimizations, and bug fixes. ### Source excerpt LLVM 21.1 have been released. As usual, I maintain lld/ELF and have added some notes to https://github.com/llvm/llvm-project/blob/release/21.x/lld/docs/ReleaseNotes.rst. I've meticulously reviewed nearly all the patches that are not authored by me. I'll delve into some of the key changes. ## Nix Weekly Recap: 2024-03-24 DevFeed: [Nix Weekly Recap: 2024-03-24]() Original publisher: [Read original article]() Published: 2024-03-24T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Rust](), [Secrets Management](), [migration](), [Security](), [modules](), [patches]() Tags: [announcements](), [migration](), [modules](), [patches](), [recap](), [release](), [secrets-management](), [security](), [weekly]() ### AI overview A weekly recap of Nix community activity covering the Devenv 1.0 rewrite from Python to Rust, NixOS secrets-management materials, new packages and modules, and security fixes. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## How to Play Grand Poo World 3 DevFeed: [How to Play Grand Poo World 3]() Original publisher: [Read original article]() Author: David Walsh Published: 2023-11-28T00:35:41Z Content type: tutorial Language: en Sources: [David Walsh]() Topics: [coding](), [Emulator](), [patches](), [Open Source](), [file]() Tags: [coding](), [emulator](), [game](), [games](), [how-to](), [mario](), [open-source](), [patches]() ### AI overview A tutorial explaining how to assemble the files and utilities needed to patch a clean Super Mario World ROM with Grand Poo World 3, including validation and emulator options for macOS and Windows. ### Source excerpt The underground world of creating and streaming Super Mario World-based ROM hacks continues to gain popularity. This popularity is a tribute to the creativity of gamers and the quality of the original 30 year old video game's mechanics. Over the past decade, incredible ROM hacks like Grand Poo World 1 and 2, Invictus, and Dram [...] The post How to Play Grand Poo World 3 appeared first on David Walsh Blog. ## Mobian's PinePhone Kernel Support and the Loss of Cross-Distribution Collaboration DevFeed: [Mobian's PinePhone Kernel Support and the Loss of Cross-Distribution Collaboration]() Original publisher: [Read original article]() Author: Mobian team Published: 2023-10-10T00:00:00Z Content type: opinion Language: en Sources: [Mobian's Blog]() Topics: [Linux Kernel](), [Mobile](), [patches](), [Hardware]() Tags: [community](), [hardware](), [linux-kernel](), [mobile](), [patches]() ### AI overview Mobian reflects on the difficulties of maintaining support for the original PinePhone. The article argues that separate kernel trees and reduced cross-distribution collaboration left the community dependent on a small number of maintainers and created a single point of failure. ### Source excerpt Mobian started as a hobby project, triggered by the excitement of finally being able to hack one's mobile phone at will. It is fair to say that the device that made it possible back then was the original PinePhone. However, after running once again into the same difficulties we experienced over and over, we're wondering whether maintaining support for this device is still worth the effort... Of kernels and men In the beginning, the mobile Linux world was full of happy people, hacking on many different aspects of the system in a very disorganized but fruitful way, one of those aspects being the Linux kernel. Back then there was a single reference source tree, maintained under the PINE64 umbrella (but still being a community effort, no one being funded in any way to work on this kernel). Things were obviously not ideal, however many talented people were talking to each other, trying to improve hardware support and fix the many bugs we were experiencing at this point. Until, I don't quite remember how, it all turned into a race, in which the goal was to have better (or at least identical) support than the neighbouring projects. In particular, one very skilled developer set to solve many of the problems we had back then, and published their work as a separate repo. Several mobile distributions quickly switched to this kernel, effectively abandoning the shared kernel source we were all using until then. This resulted in a loss of interest and, ultimately, collaboration on the kernel ceased: some ended up using megi's kernel directly, while Mobian forked the "Pine64" one and cherry-picked interesting patches from megi's tree, but it all happened without further cross-distro discussions. Our single reference tree was then left rotting (the last kernel compatible with the PinePhone being based on 5.9, which was released nearly 3 years ago!) and unmaintained since then. A single point of failure The end result can be summed up as follows: those relying on megi's kernel depend ## Making unwinding through JIT-ed code scalable - Replacing the gcc hooks DevFeed: [Making unwinding through JIT-ed code scalable - Replacing the gcc hooks]() Original publisher: [Read original article]() Author: Thomas Neumann (noreply@blogger.com) Published: 2022-06-26T08:48:00Z Content type: article Language: en Sources: [Database Architects]() Topics: [gcc](), [patches](), [JIT]() Tags: [atomic](), [gcc](), [jit](), [lock-free](), [mutex](), [patches]() ### AI overview This article explains patches to GCC that replace a globally locked list of unwinding frames with a read-optimized B-tree. The change enables concurrent registration, deregistration, and lock-free lookups, while keeping frames immutable during unwinding on platforms that support atomics. ### Source excerpt This article is part of the series about scalable unwinding that starts here. As discussed in the previous article, the gcc mechanism does not scale because it uses a global lock to protect its list of unwinding frames. To solve that problem, we replace that list with a read-optimized b-tree that allows for concurrent reads and writes. In this article we just discuss the patches to gcc necessary to enable that mechanism, the b-tree itself is discussed in subsequent articles. We start by replacing the old fast path mechanism with a b-tree root: index 8ee55be5675..d546b9e4c43 100644 --- a/libgcc/unwind-dw2-fde.c +++ b/libgcc/unwind-dw2-fde.c @@ -42,15 +42,34 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If not, see #endif #endif +#ifdef ATOMIC_FDE_FAST_PATH +#include "unwind-dw2-btree.h" + +static struct btree registered_frames; + +static void +release_registered_frames (void) __attribute__ ((destructor (110))); +static void +release_registered_frames (void) +{ + /* Release the b-tree and all frames. Frame releases that happen later are + * silently ignored */ + btree_destroy (®istered_frames); +} + +static void +get_pc_range (const struct object *ob, uintptr_t *range); +static void +init_object (struct object *ob); + +#else + /* The unseen_objects list contains objects that have been registered but not yet categorized in any way. The seen_objects list has had its pc_begin and count fields initialized at minimum, and is sorted by decreasing value of pc_begin. */ static struct object *unseen_objects; static struct object *seen_objects; -#ifdef ATOMIC_FDE_FAST_PATH -static int any_objects_registered; -#endif #ifdef __GTHREAD_MUTEX_INIT static __gthread_mutex_t object_mutex = __GTHREAD_MUTEX_INIT; @@ -78,6 +97,7 @@ init_object_mutex_once (void) static __gthread_mutex_t object_mutex; #endif #endif +#endif When the platform supports atomics (ATOMIC_FDE_FAST_PATH), we replace the whole mechanism with one b-tree, whose root is registered_frames. Neither the ## The Updates Must Go Through DevFeed: [The Updates Must Go Through]() Original publisher: [Read original article]() Author: Adam Published: 2021-04-14T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [patches](), [Microsoft](), [Malware](), [Operating system](), [Windows]() Tags: [firefox](), [macos](), [malware](), [microsoft](), [patches](), [security](), [updates]() ### AI overview The article argues that unreliable, disruptive software updates cause people to avoid applying security patches. It connects the Department of Justice's cleanup of malware from infected Microsoft Exchange mail systems with Microsoft's ongoing difficulty delivering dependable updates, and discusses the history of Microsoft's malware-removal and update tools. ### Source excerpt The timing of updates is not coincidental. ## Teleport Audit Report is Available DevFeed: [Teleport Audit Report is Available]() Original publisher: [Read original article]() Author: info@goteleport.com (Russell Jones) Published: 2018-06-01T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [audit](), [Security](), [Vulnerabilities](), [patches]() Tags: [audit](), [cybersecurity](), [patches](), [report](), [security](), [vulnerabilities]() ### AI overview Teleport announced the availability of its 2.6 audit report, produced by Cure53. The audit found no critical vulnerabilities, one high-severity directory traversal vulnerability in the auth server roles API, two medium issues, and two informational issues. The issues were patched in Teleport 2.6.0 and backported to versions 2.5.x and 2.4.x. ### Source excerpt Cure53 completed a full security audit of Teleport. Here's a brief summary of their findings with links to the full penetration test report. ## March 2018 meeting minutes DevFeed: [March 2018 meeting minutes]() Original publisher: [Read original article]() Published: 2018-04-03T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [meetings](), [Testing](), [USB](), [patches](), [systems](), [Website]() Tags: [backend](), [free](), [meetings](), [open-source](), [os](), [patches](), [react](), [reactos](), [reports](), [testing](), [usb](), [web](), [win32](), [winapi]() ### AI overview The March 2018 ReactOS meeting minutes cover project status reports, GSoC 2018, the 0.4.8 release plan, a hackfest, USB patches, and the code of conduct. Participants also discuss contributor availability, testing, Wine synchronization, NT6+ compatibility, and website maintenance needs. ### Source excerpt 2018-03-29 19:00 UTC #meeting Proceedings Meeting started at 19:08 by Colin Finck Point 1: Status Reports Point 2: GSoC Point 3: 0.4.8 Status and Release Planning Point 4: Hackfest Point 5: USB Patches Point 6: Code of Conduct Point 1: Status Reports Aleksey Bragin has been busy with his full time job as CTO. He doesn't have enough time for ReactOS, and suggests to elect a new Project Coordinator. He notes that he really enjoyed his time in the Project Coordinator position, but feels someone else could do the job better right now. [Next page]()