From: Wenshan Lan <jetlan9@163.com>
To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, vinicius.gomes@intel.com,
dave.jiang@intel.com, vkoul@kernel.org, jetlan9@163.com
Subject: [PATCH 6.6.y v2 0/2] dmaengine: idxd: fix event log crash and memory leak on FLR
Date: Sat, 9 May 2026 15:48:20 +0800 [thread overview]
Message-ID: <20260509074822.2587-1-jetlan9@163.com> (raw)
v1->v2: add commit 52d2edea0d63c ("dmaengine: idxd: Fix crash when the event log is disabled")
Backport of two upstream fixes for the dmaengine idxd event log handling
in drivers/dma/idxd/device.c. These fix a crash and a memory leak when
the event log is disabled or a Function Level Reset (FLR) occurs.
Backport notes:
- Commit 8a5084ab3af8: The upstream fix also touches idxd_device_config_restore(),
which does not exist in v6.6 (introduced in 6.14 via commit 6078a315aec1). Only
the idxd_device_evl_free() NULL check portion was backported.
- Commit 2ea19af4a590: Clean cherry-pick, no conflicts.
Vinicius Costa Gomes (2):
dmaengine: idxd: Fix crash when the event log is disabled
dmaengine: idxd: Fix leaking event log memory
drivers/dma/idxd/device.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-09 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 7:48 Wenshan Lan [this message]
2026-05-09 7:48 ` [PATCH 6.6.y v2 1/2] dmaengine: idxd: Fix crash when the event log is disabled Wenshan Lan
2026-05-09 7:48 ` [PATCH 6.6.y v2 2/2] dmaengine: idxd: Fix leaking event log memory Wenshan Lan
2026-05-09 14:32 ` [PATCH 6.6.y v2 0/2] dmaengine: idxd: fix event log crash and memory leak on FLR Sasha Levin
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=20260509074822.2587-1-jetlan9@163.com \
--to=jetlan9@163.com \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vinicius.gomes@intel.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