<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - LinkedIn - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ LinkedIn News feed</description>
    <item>
      <title>How LinkedIn Identified a Kernel Lock Contention Issue Causing Recurring System Freezes</title>
      <link>https://www.infoq.com/news/2026/05/linkedin-kernel-lock-freeze/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=LinkedIn-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/05/linkedin-kernel-lock-freeze/en/headerimage/linkedin-kernel-lock-freeze-1779903552098.jpg"/&gt;&lt;p&gt;When LinkedIn engineers encountered short-lived, recurring outages where the database powering their user feed became unavailable and then recovered without leaving helpful traces, they had to devise a novel approach to uncover the root cause using off-CPU profiling with eBPF.&lt;/p&gt; &lt;i&gt;By Sergio De Simone&lt;/i&gt;</description>
      <category>Profilers</category>
      <category>Availability</category>
      <category>Memory</category>
      <category>Monitoring</category>
      <category>Linux</category>
      <category>Rust</category>
      <category>eBPF</category>
      <category>LinkedIn</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 27 May 2026 18:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/05/linkedin-kernel-lock-freeze/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=LinkedIn-news</guid>
      <dc:creator>Sergio De Simone</dc:creator>
      <dc:date>2026-05-27T18:00:00Z</dc:date>
      <dc:identifier>/news/2026/05/linkedin-kernel-lock-freeze/en</dc:identifier>
    </item>
  </channel>
</rss>
