From: "Linga, Pavan Kumar" <pavan.kumar.linga@intel.com>
To: Simon Horman <horms@kernel.org>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<stable@vger.kernel.org>, Tarun K Singh <tarun.k.singh@intel.com>
Subject: Re: [PATCH iwl-net 2/2] idpf: fix idpf_vc_core_init error path
Date: Fri, 25 Oct 2024 10:11:35 -0700 [thread overview]
Message-ID: <8adfb7b5-0f55-4b89-a4ac-300b2c906268@intel.com> (raw)
In-Reply-To: <20241024143939.GQ1202098@kernel.org>
On 10/24/2024 7:39 AM, Simon Horman wrote:
> On Tue, Oct 22, 2024 at 10:35:27AM -0700, Pavan Kumar Linga wrote:
>> In an event where the platform running the device control plane
>> is rebooted, reset is detected on the driver. It releases
>> all the resources and waits for the reset to complete. Once the
>> reset is done, it tries to build the resources back. At this
>> time if the device control plane is not yet started, then
>> the driver timeouts on the virtchnl message and retries to
>> establish the mailbox again.
>>
>> In the retry flow, mailbox is deinitialized but the mailbox
>> workqueue is still alive and polling for the mailbox message.
>> This results in accessing the released control queue leading to
>> null-ptr-deref. Fix it by unrolling the work queue cancellation
>> and mailbox deinitialization in the order which they got
>> initialized.
>>
>> Also remove the redundant scheduling of the mailbox task in
>> idpf_vc_core_init.
>
> I think it might be better to move this last change into a separate patch
> targeted at iwl rather than iwl-net. It isn't a fix, right?
>
If we do not make that change in this patch, it results in calling
cancel_delayed_work_sync twice in case of an error in idpf_vc_core_init
(err_intr_req). Looks like there aren't any side effects of calling
cancel_delayed_work_sync twice. I will remove the said changes from this
patch.
Thanks,
Pavan
>>
>> Fixes: 4930fbf419a7 ("idpf: add core init and interrupt request")
>> Fixes: 34c21fa894a1 ("idpf: implement virtchnl transaction manager")
>> Cc: stable@vger.kernel.org # 6.9+
>> Reviewed-by: Tarun K Singh <tarun.k.singh@intel.com>
>> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
>
> ...
prev parent reply other threads:[~2024-10-25 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 17:35 [PATCH iwl-net 0/2] fix reset issues Pavan Kumar Linga
2024-10-22 17:35 ` [PATCH iwl-net 1/2] idpf: avoid vport access in idpf_get_link_ksettings Pavan Kumar Linga
2024-10-22 17:35 ` [PATCH iwl-net 2/2] idpf: fix idpf_vc_core_init error path Pavan Kumar Linga
2024-10-24 14:39 ` Simon Horman
2024-10-25 17:11 ` Linga, Pavan Kumar [this message]
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=8adfb7b5-0f55-4b89-a4ac-300b2c906268@intel.com \
--to=pavan.kumar.linga@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tarun.k.singh@intel.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;
as well as URLs for NNTP newsgroup(s).