public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Askar Safin <safinaskar@gmail.com>
Cc: adrelanos@whonix.org, arraybolt3@gmail.com,
	cryptsetup@lists.linux.dev,  dm-devel@lists.linux.dev,
	gmazyland@gmail.com,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: Hard system lock-ups when using encrypted swap and RAM is exhausted
Date: Fri, 2 Jan 2026 14:46:44 +0100 (CET)	[thread overview]
Message-ID: <eb3a9746-83a0-8271-6bd6-867ecfa49aad@redhat.com> (raw)
In-Reply-To: <20251211182429.3300562-1-safinaskar@gmail.com>



On Thu, 11 Dec 2025, Askar Safin wrote:

> Mikulas Patocka <mpatocka@redhat.com>:
> > So, this is what happened to you - the machine runs out of memory, it 
> > needs to swap out some pages, dm-crypt encrypts the pages and generates 
> > write bios, the write bios are directed to the loop device, the loop 
> > device directs them to the filesystem, the filesystem attempts to allocate 
> > more memory => deadlock.
> 
> Does similar thing happen in my case? I. e. swap on top of dm-integrity on
> top of partition? Is my use case supported? (I'm not talking about
> hibernation now, just about swap.)
> 
> -- 
> Askar Safin

Hi

Dm integrity doesn't need to allocate memory when processing I/O requests 
(it reserves some memory using mempools). So, dm-integrity on the top of a 
partition should be safe.

Mikulas



  reply	other threads:[~2026-01-02 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  5:18 Hard system lock-ups when using encrypted swap and RAM is exhausted Aaron Rainbolt
2025-11-27  7:59 ` Milan Broz
2025-11-27 17:54   ` Mikulas Patocka
2025-11-27 23:24     ` Aaron Rainbolt
2025-11-28  0:51     ` Kurt Fitzner
2025-11-28 13:06       ` Mikulas Patocka
2025-12-11 18:24     ` Askar Safin
2026-01-02 13:46       ` Mikulas Patocka [this message]
2026-01-10  7:09         ` Askar Safin
2026-01-11 13:34           ` Zdenek Kabelac
2026-01-15 10:36             ` Askar Safin
2026-01-15 11:01             ` Askar Safin
2025-11-27 23:37   ` Aaron Rainbolt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb3a9746-83a0-8271-6bd6-867ecfa49aad@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=adrelanos@whonix.org \
    --cc=arraybolt3@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    --cc=dm-devel@lists.linux.dev \
    --cc=gmazyland@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=safinaskar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox