From: Chuck Lever <cel@kernel.org> To: unlisted-recipients:; (no To-header on input) Cc: Alexander Potapenko <glider@google.com>, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux.dev, linux-rdma@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com> Subject: [PATCH RFC 4/9] mm: kmsan: Add support for DMA mapping bio_vec arrays Date: Thu, 19 Oct 2023 11:25:58 -0400 [thread overview] Message-ID: <169772915869.5232.9306605321315591579.stgit@klimt.1015granger.net> (raw) In-Reply-To: <169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net> From: Chuck Lever <chuck.lever@oracle.com> Cc: Alexander Potapenko <glider@google.com> Cc: kasan-dev@googlegroups.com Cc: linux-mm@kvack.org Cc: iommu@lists.linux.dev Cc: linux-rdma@vger.kernel.org Signed-off-by: Chuck Lever <chuck.lever@oracle.com> --- include/linux/kmsan.h | 20 ++++++++++++++++++++ mm/kmsan/hooks.c | 13 +++++++++++++ 2 files changed, 33 insertions(+) diff --git a/include/linux/kmsan.h b/include/linux/kmsan.h index e0c23a32cdf0..36c581a18b30 100644 --- a/include/linux/kmsan.h +++ b/include/linux/kmsan.h @@ -18,6 +18,7 @@ struct page; struct kmem_cache; struct task_struct; struct scatterlist; +struct bio_vec; struct urb; #ifdef CONFIG_KMSAN @@ -209,6 +210,20 @@ void kmsan_handle_dma(struct page *page, size_t offset, size_t size, void kmsan_handle_dma_sg(struct scatterlist *sg, int nents, enum dma_data_direction dir); +/** + * kmsan_handle_dma_bvecs() - Handle a DMA transfer using bio_vec array. + * @bvecs: bio_vec array holding DMA buffers. + * @nents: number of scatterlist entries. + * @dir: one of possible dma_data_direction values. + * + * Depending on @direction, KMSAN: + * * checks the buffers in the bio_vec array, if they are copied to device; + * * initializes the buffers, if they are copied from device; + * * does both, if this is a DMA_BIDIRECTIONAL transfer. + */ +void kmsan_handle_dma_bvecs(struct bio_vec *bv, int nents, + enum dma_data_direction dir); + /** * kmsan_handle_urb() - Handle a USB data transfer. * @urb: struct urb pointer. @@ -321,6 +336,11 @@ static inline void kmsan_handle_dma_sg(struct scatterlist *sg, int nents, { } +static inline void kmsan_handle_dma_bvecs(struct bio_vec *bv, int nents, + enum dma_data_direction dir) +{ +} + static inline void kmsan_handle_urb(const struct urb *urb, bool is_out) { } diff --git a/mm/kmsan/hooks.c b/mm/kmsan/hooks.c index 5d6e2dee5692..87846011c9bd 100644 --- a/mm/kmsan/hooks.c +++ b/mm/kmsan/hooks.c @@ -358,6 +358,19 @@ void kmsan_handle_dma_sg(struct scatterlist *sg, int nents, dir); } +void kmsan_handle_dma_bvecs(struct bio_vec *bvecs, int nents, + enum dma_data_direction dir) +{ + struct bio_vec *item; + int i; + + for (i = 0; i < nents; i++) { + item = &bvecs[i]; + kmsan_handle_dma(bv_page(item), item->bv_offset, item->bv_len, + dir); + } +} + /* Functions from kmsan-checks.h follow. */ void kmsan_poison_memory(const void *address, size_t size, gfp_t flags) {
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Lever <cel@kernel.org> Cc: Alexander Potapenko <glider@google.com>, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux.dev, linux-rdma@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com> Subject: [PATCH RFC 4/9] mm: kmsan: Add support for DMA mapping bio_vec arrays Date: Thu, 19 Oct 2023 11:25:58 -0400 [thread overview] Message-ID: <169772915869.5232.9306605321315591579.stgit@klimt.1015granger.net> (raw) In-Reply-To: <169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net> From: Chuck Lever <chuck.lever@oracle.com> Cc: Alexander Potapenko <glider@google.com> Cc: kasan-dev@googlegroups.com Cc: linux-mm@kvack.org Cc: iommu@lists.linux.dev Cc: linux-rdma@vger.kernel.org Signed-off-by: Chuck Lever <chuck.lever@oracle.com> --- include/linux/kmsan.h | 20 ++++++++++++++++++++ mm/kmsan/hooks.c | 13 +++++++++++++ 2 files changed, 33 insertions(+) diff --git a/include/linux/kmsan.h b/include/linux/kmsan.h index e0c23a32cdf0..36c581a18b30 100644 --- a/include/linux/kmsan.h +++ b/include/linux/kmsan.h @@ -18,6 +18,7 @@ struct page; struct kmem_cache; struct task_struct; struct scatterlist; +struct bio_vec; struct urb; #ifdef CONFIG_KMSAN @@ -209,6 +210,20 @@ void kmsan_handle_dma(struct page *page, size_t offset, size_t size, void kmsan_handle_dma_sg(struct scatterlist *sg, int nents, enum dma_data_direction dir); +/** + * kmsan_handle_dma_bvecs() - Handle a DMA transfer using bio_vec array. + * @bvecs: bio_vec array holding DMA buffers. + * @nents: number of scatterlist entries. + * @dir: one of possible dma_data_direction values. + * + * Depending on @direction, KMSAN: + * * checks the buffers in the bio_vec array, if they are copied to device; + * * initializes the buffers, if they are copied from device; + * * does both, if this is a DMA_BIDIRECTIONAL transfer. + */ +void kmsan_handle_dma_bvecs(struct bio_vec *bv, int nents, + enum dma_data_direction dir); + /** * kmsan_handle_urb() - Handle a USB data transfer. * @urb: struct urb pointer. @@ -321,6 +336,11 @@ static inline void kmsan_handle_dma_sg(struct scatterlist *sg, int nents, { } +static inline void kmsan_handle_dma_bvecs(struct bio_vec *bv, int nents, + enum dma_data_direction dir) +{ +} + static inline void kmsan_handle_urb(const struct urb *urb, bool is_out) { } diff --git a/mm/kmsan/hooks.c b/mm/kmsan/hooks.c index 5d6e2dee5692..87846011c9bd 100644 --- a/mm/kmsan/hooks.c +++ b/mm/kmsan/hooks.c @@ -358,6 +358,19 @@ void kmsan_handle_dma_sg(struct scatterlist *sg, int nents, dir); } +void kmsan_handle_dma_bvecs(struct bio_vec *bvecs, int nents, + enum dma_data_direction dir) +{ + struct bio_vec *item; + int i; + + for (i = 0; i < nents; i++) { + item = &bvecs[i]; + kmsan_handle_dma(bv_page(item), item->bv_offset, item->bv_len, + dir); + } +} + /* Functions from kmsan-checks.h follow. */ void kmsan_poison_memory(const void *address, size_t size, gfp_t flags) {
next prev parent reply other threads:[~2023-10-19 15:26 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-19 15:25 [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 15:25 ` [PATCH RFC 1/9] dma-debug: Fix a typo in a debugging eye-catcher Chuck Lever 2023-10-20 4:49 ` Christoph Hellwig 2023-10-20 13:38 ` Chuck Lever III 2023-10-23 5:56 ` Christoph Hellwig 2023-10-19 15:25 ` [PATCH RFC 2/9] bvec: Add bio_vec fields to manage DMA mapping Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 15:25 ` [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays Chuck Lever 2023-10-19 15:25 ` Chuck Lever 2023-10-19 21:38 ` kernel test robot 2023-10-19 23:21 ` Chuck Lever III 2023-10-23 2:43 ` Liu, Yujie 2023-10-23 14:27 ` Chuck Lever III 2023-10-19 21:49 ` kernel test robot 2023-10-19 15:25 ` Chuck Lever [this message] 2023-10-19 15:25 ` [PATCH RFC 4/9] mm: kmsan: Add support for DMA " Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 5/9] dma-direct: Support direct " Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 6/9] DMA-API: Add dma_sync_bvecs_for_cpu() and dma_sync_bvecs_for_device() Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 7/9] DMA: Add dma_map_bvecs_attrs() Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 22:10 ` kernel test robot 2023-10-19 15:26 ` [PATCH RFC 8/9] iommu/dma: Support DMA-mapping a bio_vec array Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:26 ` [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Chuck Lever 2023-10-19 15:26 ` Chuck Lever 2023-10-19 15:53 ` [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Matthew Wilcox 2023-10-19 17:48 ` Chuck Lever 2023-10-20 4:58 ` Christoph Hellwig 2023-10-20 10:30 ` Robin Murphy 2023-10-23 5:59 ` Christoph Hellwig 2023-10-19 16:43 ` Robin Murphy 2023-10-19 17:53 ` Jason Gunthorpe
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=169772915869.5232.9306605321315591579.stgit@klimt.1015granger.net \ --to=cel@kernel.org \ --cc=chuck.lever@oracle.com \ --cc=glider@google.com \ --cc=iommu@lists.linux.dev \ --cc=kasan-dev@googlegroups.com \ --cc=linux-mm@kvack.org \ --cc=linux-rdma@vger.kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.