From: Emil Tantilov <emil.s.tantilov@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
aleksandr.loktionov@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bigeasy@linutronix.de,
clrkwllms@kernel.org, rostedt@goodmis.org,
linux-rt-devel@lists.linux.dev, sgzhang@google.com,
boolli@google.com
Subject: [PATCH iwl-net 2/3] idpf: set the payload size before calling the async handler
Date: Mon, 16 Mar 2026 16:28:18 -0700 [thread overview]
Message-ID: <20260316232819.6872-3-emil.s.tantilov@intel.com> (raw)
In-Reply-To: <20260316232819.6872-1-emil.s.tantilov@intel.com>
Set the payload size before forwarding the reply to the async handler.
Without this, xn->reply_sz will be 0 and idpf_mac_filter_async_handler()
will never get past the size check.
Fixes: 34c21fa894a1 ("idpf: implement virtchnl transaction manager")
Signed-off-by: Emil Tantilov <emil.s.tantilov@intel.com>
Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
---
drivers/net/ethernet/intel/idpf/idpf_virtchnl.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/ethernet/intel/idpf/idpf_virtchnl.c b/drivers/net/ethernet/intel/idpf/idpf_virtchnl.c
index 21a6c9d22085..6b9692b30040 100644
--- a/drivers/net/ethernet/intel/idpf/idpf_virtchnl.c
+++ b/drivers/net/ethernet/intel/idpf/idpf_virtchnl.c
@@ -627,6 +627,10 @@ idpf_vc_xn_forward_reply(struct idpf_adapter *adapter,
err = -ENXIO;
goto out_unlock;
case IDPF_VC_XN_ASYNC:
+ /* Set reply_sz from the actual payload so that async_handler
+ * can evaluate the response.
+ */
+ xn->reply_sz = ctlq_msg->data_len;
err = idpf_vc_xn_forward_async(adapter, xn, ctlq_msg);
idpf_vc_xn_unlock(xn);
idpf_vc_xn_push_free(adapter->vcxn_mngr, xn);
--
2.37.3
next prev parent reply other threads:[~2026-03-16 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 23:28 [PATCH iwl-net 0/3] idpf: virtchnl locking and async fixes Emil Tantilov
2026-03-16 23:28 ` [PATCH iwl-net 1/3] idpf: improve locking around idpf_vc_xn_push_free() Emil Tantilov
2026-03-17 23:46 ` Li Li
2026-03-16 23:28 ` Emil Tantilov [this message]
2026-03-18 0:11 ` [PATCH iwl-net 2/3] idpf: set the payload size before calling the async handler Li Li
2026-03-19 16:21 ` Tantilov, Emil S
2026-03-16 23:28 ` [PATCH iwl-net 3/3] idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling Emil Tantilov
2026-03-18 0:13 ` Li Li
2026-03-17 9:00 ` [PATCH iwl-net 0/3] idpf: virtchnl locking and async fixes Sebastian Andrzej Siewior
2026-03-17 14:20 ` Tantilov, Emil S
2026-03-17 14:38 ` Sebastian Andrzej Siewior
2026-03-17 19:30 ` Tantilov, Emil S
2026-03-18 7:24 ` Sebastian Andrzej Siewior
2026-03-18 13:06 ` Tantilov, Emil S
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=20260316232819.6872-3-emil.s.tantilov@intel.com \
--to=emil.s.tantilov@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=boolli@google.com \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rostedt@goodmis.org \
--cc=sgzhang@google.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