From: Chris Lew <quic_clew@quicinc.com>
To: Youssef Samir <quic_yabdulra@quicinc.com>, <mani@kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <andersson@kernel.org>
Cc: <quic_jhugo@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Carl Vanderlip <quic_carlv@quicinc.com>
Subject: Re: [PATCH] net: qrtr: Update packets cloning when broadcasting
Date: Thu, 19 Sep 2024 06:35:51 -0700 [thread overview]
Message-ID: <9e23310b-c165-446f-9e99-c1bf61fe3e83@quicinc.com> (raw)
In-Reply-To: <00293616-d738-48eb-becc-981a6ad86493@quicinc.com>
On 9/17/2024 10:25 AM, Youssef Samir wrote:
> Hi Chris,
>
> On 9/17/2024 3:59 PM, Chris Lew wrote:
>> Hi Youssef,
>>
>> On 9/16/2024 10:08 AM, Youssef Samir wrote:
>>> When broadcasting data to multiple nodes via MHI, using skb_clone()
>>> causes all nodes to receive the same header data. This can result in
>>> packets being discarded by endpoints, leading to lost data.
>>>
>>> This issue occurs when a socket is closed, and a QRTR_TYPE_DEL_CLIENT
>>> packet is broadcasted. All nodes receive the same destination node ID,
>>> causing the node connected to the client to discard the packet and
>>> remain unaware of the client's deletion.
>>>
>>
>> I guess this never happens for the SMD/RPMSG transport because the skb is consumed within the context of qrtr_node_enqueue where as MHI queues the skb to be transmitted later.
>>
>> Does the duplicate destination node ID match the last node in the qrtr_all_nodes list?
>
> Yes, it always matches the last node in the qrtr_all_nodes list.
>
Thanks for the confirmation, we haven't seen this before since most of
our platforms usually only use one MHI qrtr node.
Reviewed-by: Chris Lew <quic_clew@quicinc.com>
>>
>>
>>> Replace skb_clone() with pskb_copy(), to create a separate copy of
>>> the header for each sk_buff.
>>>
>>> Fixes: bdabad3e363d ("net: Add Qualcomm IPC router")
>>> Signed-off-by: Youssef Samir <quic_yabdulra@quicinc.com>
>>> Reviewed-by: Jeffery Hugo <quic_jhugo@quicinc.com>
>>> Reviewed-by: Carl Vanderlip <quic_carlv@quicinc.com>
>>> ---
>>> net/qrtr/af_qrtr.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/net/qrtr/af_qrtr.c b/net/qrtr/af_qrtr.c
>>> index 41ece61eb57a..00c51cf693f3 100644
>>> --- a/net/qrtr/af_qrtr.c
>>> +++ b/net/qrtr/af_qrtr.c
>>> @@ -884,7 +884,7 @@ static int qrtr_bcast_enqueue(struct qrtr_node *node, struct sk_buff *skb,
>>> mutex_lock(&qrtr_node_lock);
>>> list_for_each_entry(node, &qrtr_all_nodes, item) {
>>> - skbn = skb_clone(skb, GFP_KERNEL);
>>> + skbn = pskb_copy(skb, GFP_KERNEL);
>>> if (!skbn)
>>> break;
>>> skb_set_owner_w(skbn, skb->sk);
>
next prev parent reply other threads:[~2024-09-19 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 17:08 Youssef Samir
2024-09-17 14:59 ` Chris Lew
2024-09-17 17:25 ` Youssef Samir
2024-09-19 13:35 ` Chris Lew [this message]
2024-09-24 9:02 ` patchwork-bot+netdevbpf
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=9e23310b-c165-446f-9e99-c1bf61fe3e83@quicinc.com \
--to=quic_clew@quicinc.com \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_yabdulra@quicinc.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
all inboxes | Powered by JetHome®