From: Dave Jiang <dave.jiang@intel.com>
To: n.shubin@yadro.com, Vinod Koul <vkoul@kernel.org>,
Logan Gunthorpe <logang@deltatee.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Nikita Shubin <nikita.shubin@maquefel.me>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@yadro.com
Subject: Re: [PATCH v2 0/3] dmaengine: ioatdma: Fix mem leakage series
Date: Tue, 28 May 2024 09:08:09 -0700 [thread overview]
Message-ID: <e3ec5070-abb7-4adc-9cd1-c459ca27b531@intel.com> (raw)
In-Reply-To: <20240528-ioatdma-fixes-v2-0-a9f2fbe26ab1@yadro.com>
On 5/27/24 11:09 PM, Nikita Shubin via B4 Relay wrote:
> Started with observing leakage in patch 3, investigating revealed much
> more problems in probing error path.
>
> Andy you are always welcome to review if you have a spare time.
>
> Thank you Andy and Markus for your comments.
>
> Signed-off-by: Nikita Shubin <n.shubin@yadro.com>
> ---
> Changes in v2:
> - dmaengine: ioatdma: Fix error path in ioat3_dma_probe():
> Markus:
> - fix typo
>
> - dmaengine: ioatdma: Fix kmemleak in ioat_pci_probe()
> Andy:
> - s/int/unsigned int/
> - fix spelling errors
> - trimmed kmemleak reports
>
> - Link to v1: https://lore.kernel.org/r/20240524-ioatdma-fixes-v1-0-b785f1f7accc@yadro.com
>
> ---
> Nikita Shubin (3):
> dmaengine: ioatdma: Fix leaking on version mismatch
> dmaengine: ioatdma: Fix error path in ioat3_dma_probe()
> dmaengine: ioatdma: Fix kmemleak in ioat_pci_probe()
>
> drivers/dma/ioat/init.c | 54 ++++++++++++++++++++++++++-----------------------
> 1 file changed, 29 insertions(+), 25 deletions(-)
> ---
> base-commit: 6d69b6c12fce479fde7bc06f686212451688a102
> change-id: 20240524-ioatdma-fixes-a8fccda9bd79
Thanks for the fixes.
Reviewed-by: Dave Jiang <dave.jiang@intel.com> for the series
Would be nice if someone wants to move everything to the devm_* management APIs. Would make this a lot less messy. Probably not worth the effort though given how old the driver is and no more devices are being created to use this driver.
>
> Best regards,
next prev parent reply other threads:[~2024-05-28 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:09 [PATCH v2 0/3] dmaengine: ioatdma: Fix mem leakage series Nikita Shubin via B4 Relay
2024-05-28 6:09 ` [PATCH v2 1/3] dmaengine: ioatdma: Fix leaking on version mismatch Nikita Shubin via B4 Relay
2024-05-28 6:09 ` [PATCH v2 2/3] dmaengine: ioatdma: Fix error path in ioat3_dma_probe() Nikita Shubin via B4 Relay
2024-05-28 6:09 ` [PATCH v2 3/3] dmaengine: ioatdma: Fix kmemleak in ioat_pci_probe() Nikita Shubin via B4 Relay
2024-05-28 16:08 ` Dave Jiang [this message]
2024-05-29 9:34 ` [PATCH v2 0/3] dmaengine: ioatdma: Fix mem leakage series Nikita Shubin
2024-06-11 18:27 ` Vinod Koul
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=e3ec5070-abb7-4adc-9cd1-c459ca27b531@intel.com \
--to=dave.jiang@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@yadro.com \
--cc=logang@deltatee.com \
--cc=n.shubin@yadro.com \
--cc=nikita.shubin@maquefel.me \
--cc=vkoul@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: 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