From: Leon Romanovsky <leon@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-debug: ensure mappings are created and released with matching attributes
Date: Thu, 26 Mar 2026 12:36:44 +0200 [thread overview]
Message-ID: <20260326103644.GT814676@unreal> (raw)
In-Reply-To: <f09c9c3e-ae11-440d-b36e-b88fd4645648@samsung.com>
On Wed, Mar 25, 2026 at 09:54:59PM +0100, Marek Szyprowski wrote:
> On 25.03.2026 18:56, Leon Romanovsky wrote:
> > On Wed, Mar 25, 2026 at 06:28:41PM +0100, Marek Szyprowski wrote:
> >> On 23.03.2026 21:20, Leon Romanovsky wrote:
> >>> From: Leon Romanovsky <leonro@nvidia.com>
> >>>
> >>>
> >>> The DMA API expects that callers use the same attributes when mapping
> >>> and unmapping. Add tracking to verify this and catch mismatches.
> >>>
> >>>
> >>> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> >> Applied to dma-mapping-for-next, thanks!
> > Thanks a lot.
>
> It looks I've hurries a bit too much. This patch is not yet ready for -next:
Sorry about that. It seems my test machine is a bit too optimized for my
usual workload.
At this point, I'm confident the idea is sound. I'll resend the patch after
the merge window, so we'll have a full cycle to catch and fix drivers that
do not use the same attributes.
Thanks
prev parent reply other threads:[~2026-03-26 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260323202058eucas1p1946c1763123f2ceb493ebef25165f453@eucas1p1.samsung.com>
2026-03-23 20:20 ` [PATCH] dma-debug: ensure mappings are created and released with matching attributes Leon Romanovsky
2026-03-25 17:28 ` Marek Szyprowski
2026-03-25 17:56 ` Leon Romanovsky
2026-03-25 20:54 ` Marek Szyprowski
2026-03-26 10:36 ` Leon Romanovsky [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=20260326103644.GT814676@unreal \
--to=leon@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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