diff options
author | Zhang Yuchen <zhangyuchen.lcr@bytedance.com> | 2022-10-07 12:26:16 +0300 |
---|---|---|
committer | Corey Minyard <cminyard@mvista.com> | 2022-10-17 17:51:27 +0300 |
commit | f6f1234d98cce69578bfac79df147a1f6660596c (patch) | |
tree | 0a55fbef792831ea9fb0c8af3b2703c083a0846f /drivers/input/rmi4/rmi_f55.c | |
parent | f90bc0f97f2b65af233a37b2e32fc81871a1e3cf (diff) | |
download | linux-f6f1234d98cce69578bfac79df147a1f6660596c.tar.xz |
ipmi: fix long wait in unload when IPMI disconnect
When fixing the problem mentioned in PATCH1, we also found
the following problem:
If the IPMI is disconnected and in the sending process, the
uninstallation driver will be stuck for a long time.
The main problem is that uninstalling the driver waits for curr_msg to
be sent or HOSED. After stopping tasklet, the only place to trigger the
timeout mechanism is the circular poll in shutdown_smi.
The poll function delays 10us and calls smi_event_handler(smi_info,10).
Smi_event_handler deducts 10us from kcs->ibf_timeout.
But the poll func is followed by schedule_timeout_uninterruptible(1).
The time consumed here is not counted in kcs->ibf_timeout.
So when 10us is deducted from kcs->ibf_timeout, at least 1 jiffies has
actually passed. The waiting time has increased by more than a
hundredfold.
Now instead of calling poll(). call smi_event_handler() directly and
calculate the elapsed time.
For verification, you can directly use ebpf to check the kcs->
ibf_timeout for each call to kcs_event() when IPMI is disconnected.
Decrement at normal rate before unloading. The decrement rate becomes
very slow after unloading.
$ bpftrace -e 'kprobe:kcs_event {printf("kcs->ibftimeout : %d\n",
*(arg0+584));}'
Signed-off-by: Zhang Yuchen <zhangyuchen.lcr@bytedance.com>
Message-Id: <20221007092617.87597-3-zhangyuchen.lcr@bytedance.com>
Signed-off-by: Corey Minyard <cminyard@mvista.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'drivers/input/rmi4/rmi_f55.c')
0 files changed, 0 insertions, 0 deletions