From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>,
Hamza Mahfooz <someguy@effective-light.com>,
Christoph Hellwig <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-block@vger.kernel.org, io-uring@vger.kernel.org,
linux-raid@vger.kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [Report] annoyed dma debug warning "cacheline tracking EEXIST, overlapping mappings aren't supported"
Date: Mon, 14 Oct 2024 09:17:13 -0600 [thread overview]
Message-ID: <a9fcd235-18b5-4b17-bd4f-75dc2d228e17@kernel.dk> (raw)
In-Reply-To: <ZwxzdWmYcBK27mUs@fedora>
On 10/13/24 7:27 PM, Ming Lei wrote:
> Hello Guys,
>
> I got more and more reports on DMA debug warning "cacheline tracking EEXIST,
> overlapping mappings aren't supported" in storage related tests:
This is easily triggerable with dio and reusing a buffer. But it looks
like this will only trigger if CONFIG_DMA_API_DEBUG is set, so should
not be a prod issue? If so, I'd say that debug printk should be killed.
Maybe turn it into a pr_warn_once() or something?
--
Jens Axboe
prev parent reply other threads:[~2024-10-14 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 1:27 [Report] annoyed dma debug warning "cacheline tracking EEXIST, overlapping mappings aren't supported" Ming Lei
2024-10-14 7:23 ` Hannes Reinecke
2024-10-14 7:41 ` Christoph Hellwig
2024-10-14 7:58 ` Ming Lei
2024-10-14 18:09 ` Robin Murphy
2024-10-15 1:59 ` Ming Lei
2024-10-15 2:22 ` Dan Williams
2024-10-15 4:54 ` Christoph Hellwig
2024-10-15 7:40 ` Ming Lei
2024-10-15 7:54 ` Christoph Hellwig
2024-10-15 2:31 ` Ming Lei
2024-10-14 15:17 ` Jens Axboe [this message]
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=a9fcd235-18b5-4b17-bd4f-75dc2d228e17@kernel.dk \
--to=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=someguy@effective-light.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