<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Function on The Coders Blog</title><link>https://thecodersblog.com/tag/function/</link><description>Recent content in Function on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 09 May 2026 15:58:01 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/function/index.xml" rel="self" type="application/rss+xml"/><item><title>Killswitch: Fine-Grained Security with Per-Function Mitigation</title><link>https://thecodersblog.com/killswitch-per-function-short-circuit-mitigation-2026/</link><pubDate>Sat, 09 May 2026 15:58:01 +0000</pubDate><guid>https://thecodersblog.com/killswitch-per-function-short-circuit-mitigation-2026/</guid><description>&lt;p&gt;The modern software landscape is a constant arms race. New vulnerabilities are discovered with alarming regularity, leaving systems exposed until official patches can be developed, tested, and deployed. This &amp;ldquo;patch gap&amp;rdquo; is a critical window of vulnerability, and for high-profile exploits, it can feel like an eternity. While full kernel updates or module disabling are blunt instruments for immediate protection, a new proposal in the Linux kernel, dubbed &amp;ldquo;Killswitch,&amp;rdquo; offers a more surgical approach: &lt;strong&gt;per-function short-circuit mitigation&lt;/strong&gt;. This isn&amp;rsquo;t about fixing the bug; it&amp;rsquo;s about urgently preventing its exploitation by effectively putting a single, vulnerable function on immediate, temporary lockdown.&lt;/p&gt;</description></item></channel></rss>