From: Alexander Potapenko <glider@google.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Leon Romanovsky <leonro@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
kasan-dev@googlegroups.com, kernel test robot <lkp@intel.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] kmsan: fix missed kmsan_handle_dma() signature conversion
Date: Wed, 17 Sep 2025 14:00:06 +0200 [thread overview]
Message-ID: <CAG_fn=WWw87a47aqXFBK1YpHAFStzpoU01CJTf=Eut2FgVTkMg@mail.gmail.com> (raw)
In-Reply-To: <20250917112242.GZ1086830@nvidia.com>
On Wed, Sep 17, 2025 at 1:22 PM Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> On Wed, Sep 17, 2025 at 09:37:36AM +0300, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.com>
> >
> > kmsan_handle_dma_sg() has call to kmsan_handle_dma() function which was
> > missed during conversion to physical addresses. Update that caller too
> > and fix the following compilation error:
> >
> > mm/kmsan/hooks.c:372:6: error: too many arguments to function call, expected 3, have 4
> > 371 | kmsan_handle_dma(sg_page(item), item->offset, item->length,
> > | ~~~~~~~~~~~~~~~~
> > 372 | dir);
> > | ^~~
> > mm/kmsan/hooks.c:362:19: note: 'kmsan_handle_dma' declared here
> > 362 | EXPORT_SYMBOL_GPL(kmsan_handle_dma);
> >
> > Fixes: 6eb1e769b2c1 ("kmsan: convert kmsan_handle_dma to use physical addresses")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202509170638.AMGNCMEE-lkp@intel.com/
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > ---
> > mm/kmsan/hooks.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Alexander Potapenko <glider@google.com>
next prev parent reply other threads:[~2025-09-17 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250917063825eucas1p2364dba546022ab35fdc40dc7ada6fd20@eucas1p2.samsung.com>
2025-09-17 6:37 ` Leon Romanovsky
2025-09-17 11:22 ` Jason Gunthorpe
2025-09-17 12:00 ` Alexander Potapenko [this message]
2025-09-17 12:43 ` Marek Szyprowski
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='CAG_fn=WWw87a47aqXFBK1YpHAFStzpoU01CJTf=Eut2FgVTkMg@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=kasan-dev@googlegroups.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=m.szyprowski@samsung.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