From: Vinod Koul <vkoul@kernel.org>
To: Dave Jiang <dave.jiang@intel.com>,
Logan Gunthorpe <logang@deltatee.com>,
Nikita Shubin <n.shubin@yadro.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, 11 Jun 2024 23:57:49 +0530 [thread overview]
Message-ID: <171813046978.475489.11233301770503633665.b4-ty@kernel.org> (raw)
In-Reply-To: <20240528-ioatdma-fixes-v2-0-a9f2fbe26ab1@yadro.com>
On Tue, 28 May 2024 09:09:22 +0300, Nikita Shubin 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.
>
> [...]
Applied, thanks!
[1/3] dmaengine: ioatdma: Fix leaking on version mismatch
commit: 1b11b4ef6bd68591dcaf8423c7d05e794e6aec6f
[2/3] dmaengine: ioatdma: Fix error path in ioat3_dma_probe()
commit: f0dc9fda2e0ee9e01496c2f5aca3a831131fad79
[3/3] dmaengine: ioatdma: Fix kmemleak in ioat_pci_probe()
commit: 29b7cd255f3628e0d65be33a939d8b5bba10aa62
Best regards,
--
Vinod Koul <vkoul@kernel.org>
prev parent reply other threads:[~2024-06-11 18:27 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 ` [PATCH v2 0/3] dmaengine: ioatdma: Fix mem leakage series Dave Jiang
2024-05-29 9:34 ` Nikita Shubin
2024-06-11 18:27 ` Vinod Koul [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=171813046978.475489.11233301770503633665.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=dave.jiang@intel.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 \
/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