<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Core Dumps on Nalar</title>
    <link>https://nalar.dev/tags/core-dumps/</link>
    <description>Recent content in Core Dumps on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/core-dumps/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MADV_DONTDUMP Excludes Selected Memory Mappings from Linux Core Images</title>
      <link>https://nalar.dev/madv-dontdump-excludes-selected-memory-mappings-from-linux-core-images/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/madv-dontdump-excludes-selected-memory-mappings-from-linux-core-images/</guid>
      <description>&lt;p&gt;A long-running service may keep credentials, session material, or decrypted state in memory while still relying on core images for crash diagnosis. Disabling core generation for the entire process removes diagnostic state along with sensitive state. Linux provides a narrower control: &lt;code&gt;madvise()&lt;/code&gt; with &lt;code&gt;MADV_DONTDUMP&lt;/code&gt; marks selected mappings so the kernel omits them from a core image.&lt;/p&gt;&#xA;&lt;p&gt;This mechanism changes core-dump inclusion policy for an address range. It does not make the bytes inaccessible to the process, encrypt them, erase them, or create a general barrier against process inspection. Its security value is specific to one data-exposure path: memory captured through the kernel core-dump mechanism.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
