From: Junhao He <hejunhao3@huawei.com>
To: <will@kernel.org>, <jonathan.cameron@huawei.com>,
<yangyicong@huawei.com>, <shaojijie@huawei.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linuxarm@huawei.com>,
<prime.zeng@hisilicon.com>, <hejunhao3@huawei.com>,
<chenhao418@huawei.com>
Subject: [PATCH 0/3] drivers/perf: hisi: Fixed some issues with hisi pmu
Date: Thu, 25 Apr 2024 20:46:24 +0800 [thread overview]
Message-ID: <20240425124627.13764-1-hejunhao3@huawei.com> (raw)
This patchset includes 3 bug fixes changes to hisi PMU:
- Fix out-of-bound access when valid event group in hns pmu
- Fixes the memory leak in hns pmu
- Fix out-of-bound access when valid event group in pcie pmu
Hao Chen (1):
drivers/perf: hisi: hns3: Actually use devm_add_action_or_reset()
Junhao He (2):
drivers/perf: hisi_pcie: Fix out-of-bound access when valid event
group
drivers/perf: hisi: hns3: Fix out-of-bound access when valid event
group
drivers/perf/hisilicon/hisi_pcie_pmu.c | 14 +++++++++++++-
drivers/perf/hisilicon/hns3_pmu.c | 16 ++++++++++++++--
2 files changed, 27 insertions(+), 3 deletions(-)
--
2.33.0
next reply other threads:[~2024-04-25 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:46 Junhao He [this message]
2024-04-25 12:46 ` [PATCH 1/3] drivers/perf: hisi_pcie: Fix out-of-bound access when valid event group Junhao He
2024-04-26 10:19 ` Jijie Shao
2024-04-26 15:40 ` Jonathan Cameron
2024-04-25 12:46 ` [PATCH 2/3] drivers/perf: hisi: hns3: " Junhao He
2024-04-26 10:19 ` Jijie Shao
2024-04-26 15:41 ` Jonathan Cameron
2024-04-25 12:46 ` [PATCH 3/3] drivers/perf: hisi: hns3: Actually use devm_add_action_or_reset() Junhao He
2024-04-26 10:17 ` Jijie Shao
2024-04-26 15:42 ` Jonathan Cameron
2024-04-28 8:59 ` [PATCH 0/3] drivers/perf: hisi: Fixed some issues with hisi pmu Will Deacon
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=20240425124627.13764-1-hejunhao3@huawei.com \
--to=hejunhao3@huawei.com \
--cc=chenhao418@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=shaojijie@huawei.com \
--cc=will@kernel.org \
--cc=yangyicong@huawei.com \
/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