From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 334C5330B00 for ; Sun, 11 Jan 2026 13:34:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768138468; cv=none; b=GtBpaMRqKsot6DxFO+b/CRmZMnQnYRyLFuJ15SmH+t8E/beMIGRdYcoRf/CIzlqZ5s6ewTsQM6SoeV64sKhWxVheFTYVgphIWT+YFwA72a/q7cMwL2iXOisl0DCxcIDloeJu7aFT1y8xGAI736p+iEmaNHmpZ9FTh7JFQaqruq4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768138468; c=relaxed/simple; bh=+fWdVbBVS+5ZieHGAy8VJ46GImYkPTn95DEhd287x7k=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=WAc2GYXxjJU37FK5U9SBVkvl/YKd0HqwzOZWtT35MlY8AHXSHlGVdvGpRlY003V+pHMNtlQhZm/0tEawCSLlQCKVgHkfbspmj0z8hEDZj9tuKinbFqeSyGLsymwbrUMF8gAwrNsz6N9QM+uXNS0V/omU/glxLLfSYLhT/c1av1Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=HO0If3Vd; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b=Wn5hxn/j; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="HO0If3Vd"; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b="Wn5hxn/j" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1768138466; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1iIwW7B3/vGlG96EY9fov8v0A5KtPeBu8NxLAHkqFGo=; b=HO0If3VdBsdIm9YJ+dI7KNiRsRFVj84KcCRnk/70Nb5rO3kei0oZur5cbQAS+UE1yE+S8w KVu3io4oMMpacChFCVPcsZrA2s2Cr1a9FgRLJUlXsSJJ2Vvj4fC9Owztza6eZrm3Ih59hK btq0mOvJZPkjc1DE70MGiC9+Asi8wVw= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-232-eFPL73LNOlWTCNHm3HzdKA-1; Sun, 11 Jan 2026 08:34:24 -0500 X-MC-Unique: eFPL73LNOlWTCNHm3HzdKA-1 X-Mimecast-MFC-AGG-ID: eFPL73LNOlWTCNHm3HzdKA_1768138464 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-430fcb6b2ebso3507008f8f.2 for ; Sun, 11 Jan 2026 05:34:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=google; t=1768138463; x=1768743263; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:organization:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:from:to:cc:subject:date:message-id:reply-to; bh=1iIwW7B3/vGlG96EY9fov8v0A5KtPeBu8NxLAHkqFGo=; b=Wn5hxn/jKOtxEswo/C651TIDHcaXGnR9B6C/g3IS7IxGipu7VP+mzWG2eJTGf31sZC scAOtuufklqzvYRwpSNECKk5b9FO49WDtKu+JjJt61U9oobpZiE3vBBYmMYIzFN4MGco QyyO7Xj41zUmncEBqscNjmr5sOfsdg/4pT7lrJ0pCReaoi2R24MIHelOT7EMp6h3Sw3a qTJfYIITyoo3NXHfeAjctgXSVAWFOCEqAy052EPYSjrZXoZsjShylwxhPiMLk+4VIfzq dv23p+hUF8QmPZqJCCcbhUJYGpabRe0qG3SjG/8pCaZ7TJnUIvcKXIhHgnOmUEFB457l i1ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768138463; x=1768743263; h=content-transfer-encoding:in-reply-to:organization:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=1iIwW7B3/vGlG96EY9fov8v0A5KtPeBu8NxLAHkqFGo=; b=F2eTtPHfosIw3yF6RMSTNmQhU3x3OYxAAa2SZcjeo3sVrd/srnZqdIxAc9wd0uguAG OH6yW07S15PejqToc5gMP+W51UyvW5j3X3EI/5lQ4wgHAi1pwfyywrmLDN4za30qm4rU fXvEhWJbSxXRlWDI9S5kACmJr0jRpptCwjr6UB4Z7nCsHJ5OC2VRCgJLAuzAhVQwN0xu MEvObyuuTUHNJW4SRVOq8PeFFdaAP91jB1k2+PLOiwy+1/Jm8DVwrD+XaenJ6cv+KHvA KrlIyMOruCJHyqUy0d50noVmapoHLp0Udj3GI5JwufPK89xKzJi8QH9KpGwk0QILzwD5 u5Og== X-Forwarded-Encrypted: i=1; AJvYcCXLOxoM53IOlWafj4lzpthUEONKltKlqnHQ2dkMzxP36j8ULq7fszrb4owRDv8gOeMpHArIVec2eHahfg0=@vger.kernel.org X-Gm-Message-State: AOJu0YzOFOOHU9mTX8QTScN01080Rjdrq6CZnGFkD0PRPWdxSTA5rshC Yg+y/Xw40PVswm6ild139gJOPd1Sxz4eYC2WyZwIbs2pSwHw+rtmrR0M9xkH/+7sWuvm7buvr8o AmtrrbRPnnHiJo1/Kuxhz3I/+ZNLfS7OwLQLQL1MEMmO2lFVvWTPfb/LNx46p+H9Q9Q== X-Gm-Gg: AY/fxX6pp/umWMMevl5u8GEAUSmRy8EDNOD2XDAK5NoMZa7Iq5H4Ze3bn1G7shg7O70 F3BMlYNClJjm70Xw5m4ovcGoEONsjAL7rlTX/d0CwfHdvM4f4f6EXzsIeXd8n3uQSkM+E/8vy0+ N2PmdUVT+qqEgjvNZeEQr29tb5Z65zadXzs3feTkYbdFLY8arl5baO5ckVX2f/99imDob/u6TIA 4dlUshAkgDkfnoWfSLs24wp8gK03IxJsGfUmDXbro+WpDQuET6g1iKOBLWyc9VwL2OARBZ+P39H +s5/86EXDTkrCURZ1kj21Ex6M3F83ulbuw/WfJVFtVy7kWXCGSN6/Y3ju/HQ6ovwSYzPLCBY6jH qcPocdleYSjgV X-Received: by 2002:a05:6000:18a5:b0:431:8f8:7f17 with SMTP id ffacd0b85a97d-432c362830dmr16282386f8f.10.1768138463551; Sun, 11 Jan 2026 05:34:23 -0800 (PST) X-Google-Smtp-Source: AGHT+IEUrdZET3rEay41v44TRADbajgxRdDNJp4A+SRYJqr3oi8KK+Jf1Lh89iqwj9E2Qa02SJMCbA== X-Received: by 2002:a05:6000:18a5:b0:431:8f8:7f17 with SMTP id ffacd0b85a97d-432c362830dmr16282379f8f.10.1768138463142; Sun, 11 Jan 2026 05:34:23 -0800 (PST) Received: from [192.168.0.99] ([212.20.115.16]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-432bd0dacdcsm32760448f8f.1.2026.01.11.05.34.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 11 Jan 2026 05:34:22 -0800 (PST) Message-ID: Date: Sun, 11 Jan 2026 14:34:22 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Hard system lock-ups when using encrypted swap and RAM is exhausted To: Askar Safin , Mikulas Patocka 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 References: <3f3d871a-6a86-354f-f83d-a871793a4a47@redhat.com> <20251211182429.3300562-1-safinaskar@gmail.com> Content-Language: en-US, cs From: Zdenek Kabelac Organization: RedHat In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dne 10. 01. 26 v 8:09 Askar Safin napsal(a): > On Fri, Jan 2, 2026 at 4:47 PM Mikulas Patocka wrote: >> Hi >> >> Dm integrity doesn't need to allocate memory when processing I/O requests > > Thank you for answer! > > Unfortunately, my experience shows the opposite thing. > > [[ TL;DR: my experience shows that dm-integrity journaled mode is buggy, and > non-journaled mode is not. I. e. journaled mode seems to allocate memory, and > this causes temporary (for 4 minutes) lockups (on high specced > machine). Or maybe journaled mode has > some another bug, which causes such lockups. They are not reproducible in > non-journaled mode. ]] I think it's important to decipher what and how it's blocked - I kind of suspect your system is not blocked on 'dm-integrity' itself - rather some userland app being swapped out of CPU. You probably do need to configure your systemd-oom killer to prevent getting your system to it's knees - if you run your system to the moment whether it takes 4 minutes to run a task - there is something seriously wrong with the configuration - as OOM is supposed to kill userland RAM hogging task much earlier (possibly even your overbloated google chrome APP if it run out of bounds). So I think you should also show whole device tree of your system and some more information - so there is even 'remote' chance trying to reproduce your scenario. Regards Zdenek