From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Jinjian Song <jinjian.song@fibocom.com>,
<chandrashekar.devegowda@intel.com>,
<chiranjeevi.rapolu@linux.intel.com>, <haijun.liu@mediatek.com>,
<m.chetan.kumar@linux.intel.com>,
<ricardo.martinez@linux.intel.com>, <loic.poulain@linaro.org>,
<ryazanov.s.a@gmail.com>, <johannes@sipsolutions.net>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-doc@vger.kernel.org>,
<angelogioacchino.delregno@collabora.com>,
<linux-arm-kernel@lists.infradead.org>, <matthias.bgg@gmail.com>,
<corbet@lwn.net>, <linux-mediatek@lists.infradead.org>,
<helgaas@kernel.org>, <danielwinkler@google.com>,
<korneld@google.com>, <andrew+netdev@lunn.ch>, <horms@kernel.org>
Subject: Re: [net-next v1] net: wwan: t7xx: Fix FSM command timeout issue
Date: Thu, 12 Dec 2024 12:01:51 +0100 [thread overview]
Message-ID: <b409c23a-0b6f-458c-8e34-039338e799c0@intel.com> (raw)
In-Reply-To: <20241212105555.10364-1-jinjian.song@fibocom.com>
On 12/12/2024 11:55 AM, Jinjian Song wrote:
> When driver processes the internal state change command, it use
> asynchronous thread to process the command operation. If the main
> thread detects that the task has timed out, the asynchronous thread
> will panic when executing te completion notification because the
> main thread completion object is released.
>
> BUG: unable to handle page fault for address: fffffffffffffff8
> PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> RIP: 0010:complete_all+0x3e/0xa0
> [...]
> Call Trace:
> <TASK>
> ? __die_body+0x68/0xb0
> ? page_fault_oops+0x379/0x3e0
> ? exc_page_fault+0x69/0xa0
> ? asm_exc_page_fault+0x22/0x30
> ? complete_all+0x3e/0xa0
> fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)]
> ? __pfx_autoremove_wake_function+0x10/0x10
> kthread+0xd8/0x110
> ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)]
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x38/0x50
> ? __pfx_kthread+0x10/0x10
> ret_from_fork_asm+0x1b/0x30
> </TASK>
> [...]
> CR2: fffffffffffffff8
> ---[ end trace 0000000000000000 ]---
>
> After the main thread determines that the task has timed out, mark
> the completion invalid, and add judgment in the asynchronous task.
>
> Signed-off-by: Jinjian Song <jinjian.song@fibocom.com>
> ---
> drivers/net/wwan/t7xx/t7xx_state_monitor.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wwan/t7xx/t7xx_state_monitor.c b/drivers/net/wwan/t7xx/t7xx_state_monitor.c
> index 3931c7a13f5a..57f1a7730fff 100644
> --- a/drivers/net/wwan/t7xx/t7xx_state_monitor.c
> +++ b/drivers/net/wwan/t7xx/t7xx_state_monitor.c
> @@ -108,7 +108,8 @@ static void fsm_finish_command(struct t7xx_fsm_ctl *ctl, struct t7xx_fsm_command
> {
> if (cmd->flag & FSM_CMD_FLAG_WAIT_FOR_COMPLETION) {
> *cmd->ret = result;
> - complete_all(cmd->done);
> + if (cmd->done)
> + complete_all(cmd->done);
> }
>
> kfree(cmd);
> @@ -503,8 +504,10 @@ int t7xx_fsm_append_cmd(struct t7xx_fsm_ctl *ctl, enum t7xx_fsm_cmd_state cmd_id
>
> wait_ret = wait_for_completion_timeout(&done,
> msecs_to_jiffies(FSM_CMD_TIMEOUT_MS));
> - if (!wait_ret)
> + if (!wait_ret) {
> + cmd->done = NULL;
> return -ETIMEDOUT;
> + }
>
> return ret;
> }
If this is a fix then should be targeted to net and not net-next
and probably should have Fixes: tag.
next prev parent reply other threads:[~2024-12-12 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 10:55 [net-next v1] net: wwan: t7xx: Fix FSM command timeout issue Jinjian Song
2024-12-12 11:01 ` Mateusz Polchlopek [this message]
2024-12-13 2:55 ` Jinjian Song
2024-12-12 16:15 ` Bjorn Helgaas
2024-12-13 2:57 ` Jinjian Song
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=b409c23a-0b6f-458c-8e34-039338e799c0@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chiranjeevi.rapolu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=danielwinkler@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=helgaas@kernel.org \
--cc=horms@kernel.org \
--cc=jinjian.song@fibocom.com \
--cc=johannes@sipsolutions.net \
--cc=korneld@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.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