From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 30857C4332F for ; Mon, 30 Oct 2023 14:09:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231518AbjJ3OJu (ORCPT ); Mon, 30 Oct 2023 10:09:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59084 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229514AbjJ3OJu (ORCPT ); Mon, 30 Oct 2023 10:09:50 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 356C0E1 for ; Mon, 30 Oct 2023 07:09:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1698674940; 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: in-reply-to:in-reply-to:references:references; bh=dOFRZkTKK9Z0bMd9xnhKPQO2WNoW7oCCTYa8Hwz84I8=; b=bz4pKzwzQPWtZmXPQ8Zl/mFx4fngTAVN/Kinc4J52VkH4S702PPUDpwVZyPFuFD1mNJTwk bB6tCTl2weKG3GUVaOXUXEaPmRLi1eW5iv+CqcT1AtOBLEunyJNQ5L5HEGDcLCQj8E/t/4 oLc/Amc7yvkTLaU3M+OG5D6yjSDqZ6U= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-627-j40fAQMlM6aMhm1JptNM3g-1; Mon, 30 Oct 2023 10:08:57 -0400 X-MC-Unique: j40fAQMlM6aMhm1JptNM3g-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3AC63185A781; Mon, 30 Oct 2023 14:08:56 +0000 (UTC) Received: from file1-rdu.file-001.prod.rdu2.dc.redhat.com (unknown [10.11.5.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2A2621C060AE; Mon, 30 Oct 2023 14:08:56 +0000 (UTC) Received: by file1-rdu.file-001.prod.rdu2.dc.redhat.com (Postfix, from userid 12668) id 1763530C72AB; Mon, 30 Oct 2023 14:08:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by file1-rdu.file-001.prod.rdu2.dc.redhat.com (Postfix) with ESMTP id 148423D99F; Mon, 30 Oct 2023 15:08:56 +0100 (CET) Date: Mon, 30 Oct 2023 15:08:56 +0100 (CET) From: Mikulas Patocka To: =?ISO-8859-15?Q?Marek_Marczykowski-G=F3recki?= cc: Jan Kara , Vlastimil Babka , Andrew Morton , Matthew Wilcox , Michal Hocko , stable@vger.kernel.org, regressions@lists.linux.dev, Alasdair Kergon , Mike Snitzer , dm-devel@lists.linux.dev, linux-mm@kvack.org Subject: Re: Intermittent storage (dm-crypt?) freeze - regression 6.4->6.5 In-Reply-To: Message-ID: References: <89320668-67a2-2a41-e577-a2f561e3dfdd@suse.cz> <818a23f2-c242-1c51-232d-d479c3bcbb6@redhat.com> <18a38935-3031-1f35-bc36-40406e2e6fd2@suse.cz> <3514c87f-c87f-f91f-ca90-1616428f6317@redhat.com> <1a47fa28-3968-51df-5b0b-a19c675cc289@suse.cz> <20231030122513.6gds75hxd65gu747@quack3> MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="185210117-1250732461-1698674809=:1161929" Content-ID: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.7 Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --185210117-1250732461-1698674809=:1161929 Content-Type: text/plain; CHARSET=ISO-8859-15 Content-Transfer-Encoding: 8BIT Content-ID: <2e223827-e6b-47b8-d026-66c8d92466bd@redhat.com> On Mon, 30 Oct 2023, Marek Marczykowski-Górecki wrote: > > Well, it would be possible that larger pages in a bio would trip e.g. bio > > splitting due to maximum segment size the disk supports (which can be e.g. > > 0xffff) and that upsets something somewhere. But this is pure > > speculation. We definitely need more debug data to be able to tell more. > > I can collect more info, but I need some guidance how :) Some patch > adding extra debug messages? > Note I collect those via serial console (writing to disk doesn't work > when it freezes), and that has some limits in the amount of data I can > extract especially when printed quickly. For example sysrq-t is too much. > Or maybe there is some trick to it, like increasing log_bug_len? If you can do more tests, I would suggest this: We already know that it works with order 3 and doesn't work with order 4. So, in the file include/linux/mmzone.h, change PAGE_ALLOC_COSTLY_ORDER from 3 to 4 and in the file drivers/md/dm-crypt.c leave "unsigned int order = PAGE_ALLOC_COSTLY_ORDER" there. Does it deadlock or not? So, that we can see whether the deadlock depends on PAGE_ALLOC_COSTLY_ORDER or whether it is just a coincidence. Mikulas --185210117-1250732461-1698674809=:1161929--