From: Myeonghun Pak <mhun512@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Ijae Kim <ae878000@gmail.com>,
Vasileios Almpanis <vasilisalmpanis@gmail.com>
Subject: [PATCH 3/4] usb: gadget: pch_udc: track successful EP0 DMA mappings
Date: Wed, 14 Oct 2026 23:49:15 -0400 [thread overview]
Message-ID: <20261015034916.2773248-4-mhun512@gmail.com> (raw)
In-Reply-To: <20261015034916.2773248-1-mhun512@gmail.com>
DMA address zero is valid, and a failed dma_map_single() does not
create a mapping to unmap. Track successful mapping explicitly so
cleanup handles both cases correctly. Return -EIO on mapping failure
instead of returning the positive dma_mapping_error() result.
This issue was identified as part of our ongoing research while
reviewing kernel code.
Fixes: f646cf94520e ("USB device driver of Topcliff PCH")
Assisted-by: LLM
Co-developed-by: Ijae Kim <ae878000@gmail.com>
Signed-off-by: Ijae Kim <ae878000@gmail.com>
Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
---
Compile-tested only.
drivers/usb/gadget/udc/pch_udc.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/udc/pch_udc.c b/drivers/usb/gadget/udc/pch_udc.c
index c360bc556cdc..38b9159e2461 100644
--- a/drivers/usb/gadget/udc/pch_udc.c
+++ b/drivers/usb/gadget/udc/pch_udc.c
@@ -328,6 +328,7 @@ struct pch_vbus_gpio_data {
* @data_requests: DMA pool for data requests
* @stp_requests: DMA pool for setup requests
* @dma_addr: DMA pool for received
+ * @dma_mapped: EP0 receive buffer has a valid DMA mapping
* @setup_data: Received setup data
* @base_addr: for mapped device memory
* @bar: PCI BAR used for mapped device memory
@@ -351,6 +352,7 @@ struct pch_udc_dev {
struct dma_pool *data_requests;
struct dma_pool *stp_requests;
dma_addr_t dma_addr;
+ bool dma_mapped;
struct usb_ctrlrequest setup_data;
void __iomem *base_addr;
unsigned short bar;
@@ -2887,7 +2889,10 @@ static int init_dma_pools(struct pch_udc_dev *dev)
dev->dma_addr = dma_map_single(&dev->pdev->dev, ep0out_buf,
UDC_EP0OUT_BUFF_SIZE * 4,
DMA_FROM_DEVICE);
- return dma_mapping_error(&dev->pdev->dev, dev->dma_addr);
+ if (dma_mapping_error(&dev->pdev->dev, dev->dma_addr))
+ return -EIO;
+ dev->dma_mapped = true;
+ return 0;
}
static int pch_udc_start(struct usb_gadget *g,
@@ -2996,7 +3001,7 @@ static void pch_udc_cleanup(struct pch_udc_dev *dev)
dma_pool_destroy(dev->stp_requests);
}
- if (dev->dma_addr)
+ if (dev->dma_mapped)
dma_unmap_single(&dev->pdev->dev, dev->dma_addr,
UDC_EP0OUT_BUFF_SIZE * 4, DMA_FROM_DEVICE);
}
next prev parent reply other threads:[~2026-10-15 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 3:49 [PATCH 0/4] usb: gadget: pch_udc: order IRQ and descriptor lifetimes Myeonghun Pak
2026-10-15 3:49 ` [PATCH 1/4] usb: gadget: pch_udc: release IRQ handlers before DMA cleanup Myeonghun Pak
2026-10-15 3:49 ` [PATCH 2/4] usb: gadget: pch_udc: initialize DMA before registering interrupt sources Myeonghun Pak
2026-10-15 3:49 ` Myeonghun Pak [this message]
2026-10-15 3:49 ` [PATCH 4/4] usb: gadget: pch_udc: free the EP0 data descriptor to its owning pool Myeonghun Pak
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=20261015034916.2773248-4-mhun512@gmail.com \
--to=mhun512@gmail.com \
--cc=ae878000@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=vasilisalmpanis@gmail.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
all inboxes | Powered by JetHome®