From: Jason Gunthorpe <jgg@nvidia•com>
To: Keith Busch <kbusch@kernel•org>
Cc: Leon Romanovsky <leon@kernel•org>,
Marek Szyprowski <m.szyprowski@samsung•com>,
Abdiel Janulgue <abdiel.janulgue@gmail•com>,
Alexander Potapenko <glider@google•com>,
Alex Gaynor <alex.gaynor@gmail•com>,
Andrew Morton <akpm@linux-foundation•org>,
Christoph Hellwig <hch@lst•de>,
Danilo Krummrich <dakr@kernel•org>,
David Hildenbrand <david@redhat•com>,
iommu@lists•linux.dev, Jason Wang <jasowang@redhat•com>,
Jens Axboe <axboe@kernel•dk>, Joerg Roedel <joro@8bytes•org>,
Jonathan Corbet <corbet@lwn•net>, Juergen Gross <jgross@suse•com>,
kasan-dev@googlegroups•com, linux-block@vger•kernel.org,
linux-doc@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-mm@kvack•org, linux-nvme@lists•infradead.org,
linuxppc-dev@lists•ozlabs.org,
linux-trace-kernel@vger•kernel.org,
Madhavan Srinivasan <maddy@linux•ibm.com>,
Masami Hiramatsu <mhiramat@kernel•org>,
Michael Ellerman <mpe@ellerman•id.au>,
"Michael S. Tsirkin" <mst@redhat•com>,
Miguel Ojeda <ojeda@kernel•org>,
Robin Murphy <robin.murphy@arm•com>,
rust-for-linux@vger•kernel.org, Sagi Grimberg <sagi@grimberg•me>,
Stefano Stabellini <sstabellini@kernel•org>,
Steven Rostedt <rostedt@goodmis•org>,
virtualization@lists•linux.dev, Will Deacon <will@kernel•org>,
xen-devel@lists•xenproject.org
Subject: Re: [PATCH v6 00/16] dma-mapping: migrate to physical address-based API
Date: Tue, 23 Sep 2025 19:22:16 -0300 [thread overview]
Message-ID: <20250923222216.GC2617119@nvidia.com> (raw)
In-Reply-To: <aNLnXwAJveHIqfz0@kbusch-mbp>
On Tue, Sep 23, 2025 at 12:30:55PM -0600, Keith Busch wrote:
> I don't have a system in this state at the moment, so we checked
> previous logs on machines running older kernels. It's extermely
> uncommon, but this error was happening prior to this series, so I don't
> think this introduced any new problem here. I'll keeping looking, but I
> don't think we'll make much progress if I can't find a more reliable
> reproducer.
Okay, that's great. It needs to get resolved but it is not this series
at fault.
Very rare is a different perspective, I mis-thought it was happening
reproducible all the time..
It seems to me it is actually a legitimate thing for userspace to be
able to trigger this cache line debug. If you do concurrent O_DIRECT
to the very same memory it should trigger if I read it right..
So it may not even be an actual bug???
Jason
next prev parent reply other threads:[~2025-09-23 22:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250909132821eucas1p1051ce9e0270ddbf520e105c913fa8db6@eucas1p1.samsung.com>
2025-09-09 13:27 ` [PATCH v6 00/16] dma-mapping: migrate to physical address-based API Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 01/16] dma-mapping: introduce new DMA attribute to indicate MMIO memory Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 02/16] iommu/dma: implement DMA_ATTR_MMIO for dma_iova_link() Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 03/16] dma-debug: refactor to use physical addresses for page mapping Leon Romanovsky
2025-09-09 19:37 ` Leon Romanovsky
2025-09-10 5:26 ` Leon Romanovsky
2025-09-10 11:58 ` Jason Gunthorpe
2025-09-11 22:23 ` Marek Szyprowski
2025-09-09 13:27 ` [PATCH v6 04/16] dma-mapping: rename trace_dma_*map_page to trace_dma_*map_phys Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 05/16] iommu/dma: rename iommu_dma_*map_page to iommu_dma_*map_phys Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 06/16] iommu/dma: implement DMA_ATTR_MMIO for iommu_dma_(un)map_phys() Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 07/16] dma-mapping: convert dma_direct_*map_page to be phys_addr_t based Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 08/16] kmsan: convert kmsan_handle_dma to use physical addresses Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 09/16] dma-mapping: implement DMA_ATTR_MMIO for dma_(un)map_page_attrs() Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 10/16] xen: swiotlb: Open code map_resource callback Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 11/16] dma-mapping: export new dma_*map_phys() interface Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 12/16] mm/hmm: migrate to physical address-based DMA mapping API Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 13/16] mm/hmm: properly take MMIO path Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 14/16] block-dma: migrate to dma_map_phys instead of map_page Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 15/16] block-dma: properly take MMIO path Leon Romanovsky
2025-09-09 13:27 ` [PATCH v6 16/16] nvme-pci: unmap MMIO pages with appropriate interface Leon Romanovsky
2025-09-11 22:25 ` [PATCH v6 00/16] dma-mapping: migrate to physical address-based API Marek Szyprowski
2025-09-12 9:03 ` Leon Romanovsky
2025-09-19 16:08 ` Keith Busch
2025-09-20 15:53 ` Leon Romanovsky
2025-09-21 0:47 ` Keith Busch
2025-09-23 17:09 ` Jason Gunthorpe
2025-09-23 18:30 ` Keith Busch
2025-09-23 22:22 ` Jason Gunthorpe [this message]
2025-09-23 22:35 ` Keith Busch
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=20250923222216.GC2617119@nvidia.com \
--to=jgg@nvidia$(echo .)com \
--cc=abdiel.janulgue@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alex.gaynor@gmail$(echo .)com \
--cc=axboe@kernel$(echo .)dk \
--cc=corbet@lwn$(echo .)net \
--cc=dakr@kernel$(echo .)org \
--cc=david@redhat$(echo .)com \
--cc=glider@google$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=iommu@lists$(echo .)linux.dev \
--cc=jasowang@redhat$(echo .)com \
--cc=jgross@suse$(echo .)com \
--cc=joro@8bytes$(echo .)org \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=kbusch@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-nvme@lists$(echo .)infradead.org \
--cc=linux-trace-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mhiramat@kernel$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=mst@redhat$(echo .)com \
--cc=ojeda@kernel$(echo .)org \
--cc=robin.murphy@arm$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=rust-for-linux@vger$(echo .)kernel.org \
--cc=sagi@grimberg$(echo .)me \
--cc=sstabellini@kernel$(echo .)org \
--cc=virtualization@lists$(echo .)linux.dev \
--cc=will@kernel$(echo .)org \
--cc=xen-devel@lists$(echo .)xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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