From: Zhang Yuchen <zhangyuchen.lcr@bytedance.com>
To: minyard@acm.org
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, qi.zheng@linux.dev,
Zhang Yuchen <zhangyuchen.lcr@bytedance.com>
Subject: [PATCH 0/3] ipmi: fix ipmi memleak and unload bug
Date: Fri, 7 Oct 2022 17:26:14 +0800 [thread overview]
Message-ID: <20221007092617.87597-1-zhangyuchen.lcr@bytedance.com> (raw)
Our users have reported a memory leak. The IPMI driver consumes a lot of
memory.
We found this problem because IPMI was slow to release messages after
being disconnected, causing what appeared to be a memory leak.
Fix commit as:
ipmi: fix msg stack when IPMI is disconnected
Two other issues were solved in the process of solving this problem.
1. Unloading the driver takes a long time.
Fix commit as:
ipmi: fix long wait in unload when IPMI disconnect
2. Memory leaks during driver unloading.
Fix commit as:
ipmi: fix memleak when unload ipmi driver
Zhang Yuchen (3):
ipmi: fix msg stack when IPMI is disconnected
ipmi: fix long wait in unload when IPMI disconnect
ipmi: fix memleak when unload ipmi driver
drivers/char/ipmi/ipmi_kcs_sm.c | 14 ++++++++++----
drivers/char/ipmi/ipmi_msghandler.c | 5 ++++-
drivers/char/ipmi/ipmi_si_intf.c | 27 +++++++++++++++++++--------
3 files changed, 33 insertions(+), 13 deletions(-)
--
2.30.2
next reply other threads:[~2022-10-07 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 9:26 Zhang Yuchen [this message]
2022-10-07 9:26 ` [PATCH 1/3] ipmi: fix msg stack when IPMI is disconnected Zhang Yuchen
2022-10-07 19:43 ` Corey Minyard
2022-10-08 1:36 ` Yuchen Zhang
2022-10-08 11:49 ` Corey Minyard
2022-10-09 0:53 ` Yuchen Zhang
2022-10-07 9:26 ` [PATCH 2/3] ipmi: fix long wait in unload when IPMI disconnect Zhang Yuchen
2022-10-07 19:48 ` Corey Minyard
2022-10-07 9:26 ` [PATCH 3/3] ipmi: fix memleak when unload ipmi driver Zhang Yuchen
2022-10-07 19:51 ` Corey Minyard
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=20221007092617.87597-1-zhangyuchen.lcr@bytedance.com \
--to=zhangyuchen.lcr@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=qi.zheng@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).