Received-SPF: pass (google.com: domain of linux-kernel+bounces-134567-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Vinod Koul <vkoul@kernel.org>
To: Eugeniy.Paltsev@synopsys.com, dmaengine@vger.kernel.org, 
 Joao Pinto <Joao.Pinto@synopsys.com>
Cc: Martin.McKenny@synopsys.com, linux-kernel@vger.kernel.org
In-Reply-To: <1711536564-12919-1-git-send-email-jpinto@synopsys.com>
References: <1711536564-12919-1-git-send-email-jpinto@synopsys.com>
Subject: Re: [PATCH RESEND] Avoid hw_desc array overrun in dw-axi-dmac
Message-Id: <171250795567.435322.8170668108281183858.b4-ty@kernel.org>
Date: Sun, 07 Apr 2024 22:09:15 +0530
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


On Wed, 27 Mar 2024 10:49:24 +0000, Joao Pinto wrote:
> I have a use case where nr_buffers = 3 and in which each descriptor is composed by 3
> segments, resulting in the DMA channel descs_allocated to be 9. Since axi_desc_put()
> handles the hw_desc considering the descs_allocated, this scenario would result in a
> kernel panic (hw_desc array will be overrun).
> 
> To fix this, the proposal is to add a new member to the axi_dma_desc structure,
> where we keep the number of allocated hw_descs (axi_desc_alloc()) and use it in
> axi_desc_put() to handle the hw_desc array correctly.
> 
> [...]

Applied, thanks!

[1/1] Avoid hw_desc array overrun in dw-axi-dmac
      commit: 333e11bf47fa8d477db90e2900b1ed3c9ae9b697

Best regards,
-- 
~Vinod