From: Kishon Vijay Abraham I <kishon@ti.com>
To: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>,
"Vinod Koul" <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v3 0/2] dmaengine: ti: k3-udma: Fix NULL pointer dereference error
Date: Sun, 31 Oct 2021 08:40:04 +0530 [thread overview]
Message-ID: <7aeb5d55-7622-683f-bf9f-cd7eed3cc838@ti.com> (raw)
In-Reply-To: <87082448-0670-4fee-fc7b-8ead415180da@gmail.com>
Hi Peter,
On 30/10/21 12:15 pm, Péter Ujfalusi wrote:
> Hi Kishon,
>
> On 29/10/2021 18:12, Kishon Vijay Abraham I wrote:
>> NULL pointer de-reference error was observed when all the PCIe endpoint
>> functions (22 function in J721E) request a DMA channel. The issue was
>> specfically observed when using mem-to-mem copy.
>>
>> Changes from v2:
>> 1) Fix commit subject and commit log to mention bchan/rchan/tchan to NULL
>> suggested by Peter.
>
> Looks good, however the second patch also fixes the rflow. It is
> mentioned in the commit message itself.
>
> I suppose the reason for a split is that the UDMA part
> (rchan/tchan/rflow) could be backported as fix for older kernel since
> the bchan came later with BCDMA/PKTDMA support?
>
> Can you find a good Fixes tag for these?
I'll now add "Cc: <Stable@vger.kernel.org>" so that it gets merged to 5.14. It
doesn't apply cleanly to any of the other stable kernel.
>
>>
>> Changes from v1:
>> 1) Split the patch for BCDMA and PKTDMA separately
>> 2) Fixed the return value of udma_get_rflow() to 0.
>> 3) Removed the fixes tag as the patches does not directly apply to the
>> commits.
>>
>> v1 => https://lore.kernel.org/r/20210209090036.30832-1-kishon@ti.com
>> v2 => https://lore.kernel.org/r/20211027055625.11150-1-kishon@ti.com
>>
>> Kishon Vijay Abraham I (2):
>> dmaengine: ti: k3-udma: Set bchan to NULL if a channel request fail
>> dmaengine: ti: k3-udma: Set rchan/tchan to NULL if a channel request
>> fail
>
> dmaengine: ti: k3-udma: Set r/tchan or rflow to NULL if request fail
>
> would have bee a better subject line, if you feel you can send an update.
>
> Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
Thank You! Will fix and resend.
Best Regards,
Kishon
prev parent reply other threads:[~2021-10-31 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 15:12 [PATCH v3 0/2] dmaengine: ti: k3-udma: Fix NULL pointer dereference error Kishon Vijay Abraham I
2021-10-29 15:12 ` [PATCH v3 1/2] dmaengine: ti: k3-udma: Set bchan to NULL if a channel request fail Kishon Vijay Abraham I
2021-10-29 15:12 ` [PATCH v3 2/2] dmaengine: ti: k3-udma: Set rchan/tchan " Kishon Vijay Abraham I
2021-10-30 6:45 ` [PATCH v3 0/2] dmaengine: ti: k3-udma: Fix NULL pointer dereference error Péter Ujfalusi
2021-10-31 3:10 ` Kishon Vijay Abraham I [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=7aeb5d55-7622-683f-bf9f-cd7eed3cc838@ti.com \
--to=kishon@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vigneshr@ti.com \
--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