From: Sean Anderson <sean.anderson@linux.dev>
To: Christoph Hellwig <hch@lst.de>
Cc: m.szyprowski@samsung.com, robin.murphy@arm.com,
iommu@lists.linux.dev,
syzbot+95e4ef83a3024384ec7a@syzkaller.appspotmail.com
Subject: Re: [PATCH] dma-mapping: fix DMA API tracing for chained scatterlists
Date: Thu, 26 Sep 2024 11:34:50 -0400 [thread overview]
Message-ID: <f349cea1-75cf-4941-a3f7-1ee0872a1c71@linux.dev> (raw)
In-Reply-To: <20240926073348.1839850-1-hch@lst.de>
On 9/26/24 03:33, Christoph Hellwig wrote:
> scatterlist allocations can be chained, and thus all iterations need to
> use the chain-aware iterators. Switch the newly added tracing to use the
> proper iterators so that they work with chained scatterlists.
>
> Fixes: 038eb433dc14 ("dma-mapping: add tracing for dma-mapping API calls")
> Reported-by: syzbot+95e4ef83a3024384ec7a@syzkaller.appspotmail.com
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Tested-by: syzbot+95e4ef83a3024384ec7a@syzkaller.appspotmail.com
> ---
> include/trace/events/dma.h | 37 +++++++++++++++++++------------------
> 1 file changed, 19 insertions(+), 18 deletions(-)
>
> diff --git a/include/trace/events/dma.h b/include/trace/events/dma.h
> index f57f05331d7385..569f86a44aaaf4 100644
> --- a/include/trace/events/dma.h
> +++ b/include/trace/events/dma.h
> @@ -176,9 +176,9 @@ TRACE_EVENT(dma_free,
> );
>
> TRACE_EVENT(dma_map_sg,
> - TP_PROTO(struct device *dev, struct scatterlist *sg, int nents,
> + TP_PROTO(struct device *dev, struct scatterlist *sgl, int nents,
> int ents, enum dma_data_direction dir, unsigned long attrs),
> - TP_ARGS(dev, sg, nents, ents, dir, attrs),
> + TP_ARGS(dev, sgl, nents, ents, dir, attrs),
>
> TP_STRUCT__entry(
> __string(device, dev_name(dev))
> @@ -190,17 +190,17 @@ TRACE_EVENT(dma_map_sg,
> ),
>
> TP_fast_assign(
> + struct scatterlist *sg;
> int i;
>
> __assign_str(device);
> - for (i = 0; i < nents; i++)
> - ((u64 *)__get_dynamic_array(phys_addrs))[i] =
> - sg_phys(sg + i);
> - for (i = 0; i < ents; i++) {
> + for_each_sg(sgl, sg, nents, i)
> + ((u64 *)__get_dynamic_array(phys_addrs))[i] = sg_phys(sg);
> + for_each_sg(sgl, sg, ents, i) {
> ((u64 *)__get_dynamic_array(dma_addrs))[i] =
> - sg_dma_address(sg + i);
> + sg_dma_address(sg);
> ((unsigned int *)__get_dynamic_array(lengths))[i] =
> - sg_dma_len(sg + i);
> + sg_dma_len(sg);
> }
> __entry->dir = dir;
> __entry->attrs = attrs;
> @@ -222,9 +222,9 @@ TRACE_EVENT(dma_map_sg,
> );
>
> TRACE_EVENT(dma_unmap_sg,
> - TP_PROTO(struct device *dev, struct scatterlist *sg, int nents,
> + TP_PROTO(struct device *dev, struct scatterlist *sgl, int nents,
> enum dma_data_direction dir, unsigned long attrs),
> - TP_ARGS(dev, sg, nents, dir, attrs),
> + TP_ARGS(dev, sgl, nents, dir, attrs),
>
> TP_STRUCT__entry(
> __string(device, dev_name(dev))
> @@ -234,12 +234,12 @@ TRACE_EVENT(dma_unmap_sg,
> ),
>
> TP_fast_assign(
> + struct scatterlist *sg;
> int i;
>
> __assign_str(device);
> - for (i = 0; i < nents; i++)
> - ((u64 *)__get_dynamic_array(addrs))[i] =
> - sg_phys(sg + i);
> + for_each_sg(sgl, sg, nents, i)
> + ((u64 *)__get_dynamic_array(addrs))[i] = sg_phys(sg);
> __entry->dir = dir;
> __entry->attrs = attrs;
> ),
> @@ -290,9 +290,9 @@ DEFINE_EVENT(dma_sync_single, dma_sync_single_for_device,
> TP_ARGS(dev, dma_addr, size, dir));
>
> DECLARE_EVENT_CLASS(dma_sync_sg,
> - TP_PROTO(struct device *dev, struct scatterlist *sg, int nents,
> + TP_PROTO(struct device *dev, struct scatterlist *sgl, int nents,
> enum dma_data_direction dir),
> - TP_ARGS(dev, sg, nents, dir),
> + TP_ARGS(dev, sgl, nents, dir),
>
> TP_STRUCT__entry(
> __string(device, dev_name(dev))
> @@ -302,14 +302,15 @@ DECLARE_EVENT_CLASS(dma_sync_sg,
> ),
>
> TP_fast_assign(
> + struct scatterlist *sg;
> int i;
>
> __assign_str(device);
> - for (i = 0; i < nents; i++) {
> + for_each_sg(sgl, sg, nents, i) {
> ((u64 *)__get_dynamic_array(dma_addrs))[i] =
> - sg_dma_address(sg + i);
> + sg_dma_address(sg);
> ((unsigned int *)__get_dynamic_array(lengths))[i] =
> - sg_dma_len(sg + i);
> + sg_dma_len(sg);
> }
> __entry->dir = dir;
> ),
Reviewed-by: Sean Anderson <sean.anderson@linux.dev>
prev parent reply other threads:[~2024-09-26 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 7:33 [PATCH] dma-mapping: fix DMA API tracing for chained scatterlists Christoph Hellwig
2024-09-26 15:34 ` Sean Anderson [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=f349cea1-75cf-4941-a3f7-1ee0872a1c71@linux.dev \
--to=sean.anderson@linux.dev \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=syzbot+95e4ef83a3024384ec7a@syzkaller.appspotmail.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