From: Kishon Vijay Abraham I <kishon@ti.com>
To: Peter 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>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: [PATCH v3 0/2] dmaengine: ti: k3-udma: Fix NULL pointer dereference error
Date: Fri, 29 Oct 2021 20:42:49 +0530 [thread overview]
Message-ID: <20211029151251.26421-1-kishon@ti.com> (raw)
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.
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
drivers/dma/ti/k3-udma.c | 32 ++++++++++++++++++++++++++------
1 file changed, 26 insertions(+), 6 deletions(-)
--
2.17.1
next reply other threads:[~2021-10-29 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 15:12 Kishon Vijay Abraham I [this message]
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
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=20211029151251.26421-1-kishon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.