From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=74.125.82.52 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1792642840; b=s49eMDLg7EbBvn+4BzQ4BIONuz29zSjIzX0t6auyDwMfkO8W77sAJ70U/gAlg9hVFdoJ 9hSS2PAeIhuaL8mjO1tsnuSPjbzxs7N9zh75HpbjEskTVXmaJ4mKlJq8AEgtkCI6rJLCO HGbVIt3NpMZyxeTwWLSylpIuF3LiwdQyopStweq29D1LD/r0F2n3qZ1pwKeihiK2noYbg o0Ql6NP1CqbHg8NS26KemckoTCQtbiFabWDhJ54QpXhJFdJLWqc+W/BBi/FRG7xgXqno3 MBJzQ2wyn9/ceF9GU4WT0HbNiKwahlVnSqUaK0a0EOqTp1jsSUQM2kOabMSka4Ol5Iw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792642840; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: From:To:Cc:Subject:In-Reply-To:Date:Message-ID:References; bh=IYGqe8uHdvMKTGNalGzso/Hav7cwh06URO2tg9hCsgA=; b=iDwbPZSBnOVgkjYpAcUHMr7WXKM61g8huSc1vU5dphnp275J0jm2Jat3A0Ih4qWnHVY+ WhP8ghvHpLIoSi7c+qWoh4J7kQOr5qf82nhD+eOJGK1XO0VSmFPJLksaK6cimX/oLuM1H 2YkIrqgAKFM6xBKvxv77hDlJi4Q12jNnsfmPrM3lFTp5n/7/9PDVz9oHOOwRYzrgq2d/s cX4nca84qBlnzZvHI8Qn8hJch6rEHA1w8A97TTpAU3YaU7OPak6AefSa8oS7pcAHMLpMW CkhHCQRYNKu0G5AFxQp3oV9Y6q2iTrGkdRqYXlRk34CW2uPh+gEVraI6zoI9LIKSUKQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=EKm3EM+6; arc=none smtp.remote-ip=74.125.82.52 Received: from mail-dl1-f52.google.com (mail-dl1-f52.google.com [74.125.82.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7A6BB606A31A for ; Thu, 22 Oct 2026 04:20:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 7A6BB606A31A Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=EKm3EM+6 Received: by mail-dl1-f52.google.com with SMTP id a92af1059eb24-15dd124bbe7so2662368c88.1 for ; Wed, 21 Oct 2026 21:20:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1792642839; x=1793247639; darn=vger.kernel.org; h=references:message-id:date:in-reply-to:subject:cc:to:from:from:to :cc:subject:date:message-id:reply-to:content-type; bh=IYGqe8uHdvMKTGNalGzso/Hav7cwh06URO2tg9hCsgA=; b=EKm3EM+6auetdY/kjeEEjNANFJh0VAqa37m9SgxUmEVA/Z/nM0sskQ32739FoiM13L ubOlxIckCxXZN6YAGUobJ7BkDZJ0MkN7Y+odVP5HlSWT5YxIComCKEbW8QrA/NlO1E5u PZPIQs/3mcKkDgOYcUw/fEjcegXoLAV/j5lScc0Ggv/seHYB9cdvifl7E8tb8b3ojcva PISqgBZxAsU3ySrboUuKyADL4lqplo708r26YhSxHUsssxvpJWpJnLV5u3Pk2C0UqKZi vpIxKOYwlbkAkVMlGi6bZltbYeOoFxosElQhbLvB6hZ778ROFc+131N3lzjDYwGo53dE qHdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792642839; x=1793247639; h=references:message-id:date:in-reply-to:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=IYGqe8uHdvMKTGNalGzso/Hav7cwh06URO2tg9hCsgA=; b=pH7TwZWHBFfO3D/NfoX7T4gT65uhelg3BIYykEp2g3e/JYJt+8I9GzGI3a09hrK+KB hDyxQMnjgvWoVU3aiTVdPUZdu/k+5uQhmkzb/t9RbB+LD8Fa4IGhmhtu3+n7+bkSce9u It3d49Xo2cE7wi90qYbWqorvcoyi8hw6DCS6nRiOoLJACiHlwXysdwSyasCI9qX7W6iJ XCfU77o5GbPycL9e6pKxNpSpVvjG4gcMvOeviUeRvI/QSBD9h96RooU5H9IQFuvWwiFz Fm+6wkPUNO7cFLDpGhdoOeb9gK9xN3woQwVKUpCOEvO0/muw4L3MrD1Eoxd6v5dZDoYk YHWQ== X-Forwarded-Encrypted: i=1; AKwUvBwmnHrlQajiwBj0ITTlTatGQF65DdvJE2Mm52eMZiGZz5+ZRmLnItVEJn8TVqO2lmPDWzQEPvQ=@vger.kernel.org X-Gm-Message-State: AFq9FYKAhiHuzYaRUJIKjYoALaqu474e6ZU1Ntzjod6KELKIohF65RZp poF3eo6qNKycVBC0XmZl6Hwxczl2r4SJmMiMhlhD1TZp8ICyFqjzs4CT X-Gm-Gg: AYBFou1k6GcCUmtcdbBkajw5BxAZ0+Rdq0LcQsGAm7KvOOhOfXu5IE6NE5khXGazFCO iK3Onic6XKpew1oL/CD5IRUv9dqhDQOSdzzPAxTrPFPvuUSNnb/hopRWzeJwfjpD97FH02f26cm OtH9xFsha6N/0tPFSilCQuW0rusRnI1tKzGgrC0noqvCTTsEU/3SCBj+7b7WbkJdXdDUUCd6HMJ RiBldtDIyw/meUWJwcUKIBs28WsKDYT1o8trcCYg5XQUjXyDO+q9lw8EeppLIs07dhsp1AI990d wB9J+uFetxcBGxPUkSGreGnZGc6opulJQ1C97O0sYSvFW04XcRekBUJ2BCXjmySBPuiy6uJg5r8 jbGl7hImXiSRpGnmsrMDMja3ta0xTibgqUEAvoTP7hdwI9FU0mQ/aHLalViu0eADi8cDypBiUu8 rS4Fpcho2BjmC/sK/cSBut5wwn26sxqmXXVgcecoEu8YBYbqKoHQleAQQDFPDaIw7XkyZoTof7y t1iwM9+m2ZezzmrviLhPWi58LIGU5rouGIMuTaGkjVvseTYCG538w== X-Received: by 2002:a05:7022:628a:b0:144:c12b:dfc6 with SMTP id a92af1059eb24-190a80ee9a2mr7469795c88.44.1792642838435; Wed, 21 Oct 2026 21:20:38 -0700 (PDT) Received: from pve-server ([49.205.216.49]) by smtp.gmail.com with ESMTPSA id a92af1059eb24-1903ca044d4sm11690981c88.17.2026.10.21.21.20.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Oct 2026 21:20:37 -0700 (PDT) From: Ritesh Harjani (IBM) To: Muchun Song , Dan Williams , Vishal Verma , Dave Jiang , Alison Schofield Cc: Andrew Morton , Joao Martins , Muchun Song , stable@vger.kernel.org, nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org, Muchun Song Subject: Re: [PATCH] dax/pmem: fix unaligned compound devmap initialization In-Reply-To: <20261016054914.2601510-1-songmuchun@bytedance.com> Date: Thu, 22 Oct 2026 09:07:21 +0530 Message-ID: References: <20261016054914.2601510-1-songmuchun@bytedance.com> X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list + linuxppc-dev (for awareness, since I also faced the same issue on Power too, although this one is not related to PPC alone) Muchun Song writes: > Static pmem Device DAX namespaces reserve space for namespace metadata > before the user-visible data range, and may also include padding needed > to satisfy the Device DAX alignment. __dax_pmem_probe() adjusts the > dax_region range to start at the data range, but the dev_pagemap range > still starts at the beginning of the namespace. > > That is not valid for compound devmap mappings whose memmap is stored in > system RAM. Compound page initialization requires the start PFN to be > naturally aligned to the compound page size, because the head and tail > struct pages are initialized according to that geometry. If the pgmap > starts before the aligned data range, memmap_init_zone_device() can build > compound page metadata from an unaligned PFN. > > The resulting struct page layout is inconsistent with the Device DAX > mapping. A later mmap fault can then resolve the user-visible PFN through > invalid compound page metadata and hit a kernel panic while inserting the > DAX folio. > > Fix this by advancing the pgmap start to the aligned Device DAX data > range for non-altmap compound mappings. Leave base-page namespaces > unchanged, and leave the altmap path unchanged because > memmap_init_zone_device() already skips the altmap reservation itself. > > Fixes: 14606001efb4 ("device-dax: compound devmap support") > Cc: > Reported-by: Ritesh Harjani (IBM) Thanks Muchun for fixing this. With this patch I am no more seeing the following crash (tested on both Power and x86 kvm) Feel free to add for this patch. Tested-by: Ritesh Harjani (IBM) [ 4.675578] page dumped because: VM_BUG_ON_PAGE(!zone_spans_pfn(page_zone(page), pfn)) [ 4.675613] ------------[ cut here ]------------ [ 4.675615] kernel BUG at mm/page_alloc.c:373! [ 4.675626] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC PTI [ 4.678213] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.3.0-rc5-xfstests-01065-g45f4c1453cbe #33 PREEMPT(full) [ 4.678213] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 4.678213] RIP: 0010:__set_pfnblock_flags_mask.constprop.0+0xef/0x110 <...> [ 4.678213] Call Trace: [ 4.678213] [ 4.678213] pageblock_migratetype_init_range.constprop.0+0x50/0x90 [ 4.678213] memmap_init_zone_device+0x2fb/0x380 [ 4.678213] pagemap_range+0x272/0x590 [ 4.678213] memremap_pages+0x125/0x210 [ 4.678213] ? lockdep_hardirqs_on+0x7d/0x100 [ 4.678213] devm_memremap_pages+0x21/0x70 [ 4.678213] dev_dax_probe+0x1db/0x300 [ 4.678213] dax_bus_probe+0x6f/0xa0 [ 4.678213] call_driver_probe+0x24/0xf0 [ 4.678213] really_probe+0xb6/0x310 [ 4.678213] ? __pfx___device_attach_driver+0x10/0x10 [ 4.678213] __driver_probe_device+0x87/0x190 [ 4.678213] ? __pfx___device_attach_driver+0x10/0x10 [ 4.678213] driver_probe_device+0x1f/0x90 [ 4.678213] __device_attach_driver+0x89/0x130 [ 4.678213] bus_for_each_drv+0x86/0xe0 [ 4.678213] __device_attach+0xb6/0x1d0 [ 4.678213] device_initial_probe+0x40/0x60 [ 4.678213] bus_probe_device+0x3d/0xa0 [ 4.678213] device_add+0x4f0/0x6c0 [ 4.678213] __devm_create_dev_dax+0x18b/0x3f0 [ 4.678213] devm_create_dev_dax+0x21/0x40 [ 4.678213] __dax_pmem_probe+0x1c3/0x200 [ 4.678213] dax_pmem_probe+0xe/0x20 [ 4.678213] nvdimm_bus_probe+0x89/0x250 [ 4.678213] call_driver_probe+0x24/0xf0 [ 4.678213] really_probe+0xb6/0x310 [ 4.678213] ? __pfx___driver_attach+0x10/0x10 [ 4.678213] __driver_probe_device+0x87/0x190 [ 4.678213] ? __pfx___driver_attach+0x10/0x10 [ 4.678213] driver_probe_device+0x1f/0x90 [ 4.678213] __driver_attach+0xd7/0x200 [ 4.678213] bus_for_each_dev+0x79/0xc0 [ 4.678213] bus_add_driver+0x127/0x250 [ 4.678213] driver_register+0x59/0x100 [ 4.678213] ? __pfx_dax_pmem_init+0x10/0x10 [ 4.678213] do_one_initcall+0x59/0x3a0 [ 4.678213] do_initcalls+0xdd/0x1b0 [ 4.678213] kernel_init_freeable+0x16f/0x2b0 [ 4.678213] ? __pfx_kernel_init+0x10/0x10 [ 4.678213] kernel_init+0x1f/0x1d0 [ 4.678213] ret_from_fork+0x244/0x280 [ 4.678213] ? __pfx_kernel_init+0x10/0x10 [ 4.678213] ret_from_fork_asm+0x1a/0x30 [ 4.678213] > Closes: https://lore.kernel.org/r/wlrkqqvg.ritesh.list@gmail.com > Assisted-by: LLM > Signed-off-by: Muchun Song > --- > drivers/dax/pmem.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/dax/pmem.c b/drivers/dax/pmem.c > index bee93066a849..d3a9b85107b0 100644 > --- a/drivers/dax/pmem.c > +++ b/drivers/dax/pmem.c > @@ -51,6 +51,13 @@ static struct dev_dax *__dax_pmem_probe(struct device *dev) > /* adjust the dax_region range to the start of data */ > range = pgmap.range; > range.start += offset; > + /* > + * When the memmap is stored in RAM, exclude metadata and alignment > + * padding from compound page initialization. Otherwise, the pgmap > + * may start before the naturally aligned Device DAX data range. > + */ > + if (!pgmap_altmap(&pgmap) && le32_to_cpu(pfn_sb->align) > PAGE_SIZE) BTW, this check "le32_to_cpu(pfn_sb->align) > PAGE_SIZE" - Is that needed here? I am trying to understand this better - so that I can add more such testcases internally. For the test I mentioned earlier [1] - even w/o that align check, the test passes. [1]: https://lore.kernel.org/r/wlrkqqvg.ritesh.list@gmail.com -ritesh > + pgmap.range.start = range.start; > dax_region = alloc_dax_region(dev, region_id, &range, > nd_region->target_node, le32_to_cpu(pfn_sb->align), > IORESOURCE_DAX_STATIC); > > base-commit: 0fcb05b72344f40806cbe810de8872f1698bf053 > -- > 2.54.0