From: Ming Lei <[email protected]>
To: Hamza Mahfooz <[email protected]>,
Christoph Hellwig <[email protected]>,
Dan Williams <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: [Report] annoyed dma debug warning "cacheline tracking EEXIST, overlapping mappings aren't supported"
Date: Mon, 14 Oct 2024 09:27:17 +0800 [thread overview]
Message-ID: <ZwxzdWmYcBK27mUs@fedora> (raw)
Hello Guys,
I got more and more reports on DMA debug warning "cacheline tracking EEXIST,
overlapping mappings aren't supported" in storage related tests:
1) liburing
- test/iopoll-overflow.t
- test/sq-poll-dup.t
Same buffer is used in more than 1 IO.
2) raid1 driver
- same buffer is used in more than 1 bio
3) some storage utilities
- dm thin provisioning utility of thin_check
- `dt`(https://github.com/RobinTMiller/dt)
I looks like same user buffer is used in more than 1 dio.
4) some self cooked test code which does same thing with 1)
In storage stack, the buffer provider is far away from the actual DMA
controller operating code, which doesn't have the knowledge if
DMA_ATTR_SKIP_CPU_SYNC should be set.
And suggestions for avoiding this noise?
Thanks,
Ming
next reply other threads:[~2024-10-14 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 1:27 Ming Lei [this message]
2024-10-14 7:23 ` [Report] annoyed dma debug warning "cacheline tracking EEXIST, overlapping mappings aren't supported" 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
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=ZwxzdWmYcBK27mUs@fedora \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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